Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No OPTIONS? #12

Open
tlrobinson opened this issue Dec 20, 2012 · 1 comment
Open

No OPTIONS? #12

tlrobinson opened this issue Dec 20, 2012 · 1 comment

Comments

@tlrobinson
Copy link
Member

There are some arguments against using OPTIONS (caching, poor support in servers/clients):

http://www.mnot.net/blog/2012/10/29/NO_OPTIONS
http://www.mnot.net/blog/2005/04/03/options

But I don't know, I still like the idea of using OPTIONS.

@progrium
Copy link
Member

I sympathize with the argument, but I usually just address it by having to
ways to get at whatever you'd give with options. So for example, if you
were using OPTIONS as builtin help, you could do GET /resource?help ...
maybe we do something like GET /resource?block

On Thu, Dec 20, 2012 at 11:52 AM, Tom Robinson [email protected]:

There are some arguments against using OPTIONS (caching, poor support in
servers/clients):

http://www.mnot.net/blog/2012/10/29/NO_OPTIONS
http://www.mnot.net/blog/2005/04/03/options

But I don't know, I still like the idea of using OPTIONS.


Reply to this email directly or view it on GitHubhttps://github.com//issues/12.

Jeff Lindsay
http://progrium.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants