No OPTIONS?

Open tlrobinson opened this issue 13 years ago • 1 comments

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.

Dec 20 '12 19:12 tlrobinson

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/webpipes/spec/issues/12.

Jeff Lindsay http://progrium.com

Dec 21 '12 22:12 progrium