[endymi0n]

related: http://evertpot.com/dropbox-post-api/

Basically everything about the status quo is messed up.

JSON into parameters: bad.

JSON into request body: undefined with the GET method.

JSON into request body with POST: great, but we're not actually mutating anything, so it's bad practice and won't be cached by varnish/nginx + a barrage of other problems.

I really wish someone would take up on http://www.ietf.org/rfc/rfc3253 - like REPORT as an analogue to GET, just with a JSON request body. Hey, we as a community finally managed to get PUT and PATCH on track, why not this one?

[fizzbatter]

PUT and PATCH on track? I'm going to have to look into that. I had no idea progress was being made there, and i thought PUT and DELETE were basically dead.. atleast, in hopes of browsers being able to use them.

[dragonwriter]

> PUT and PATCH on track?

I'm not sure what the reference to PUT is (its a base HTTP method) but I assume that PATCH refers to getting it added as an RFC-specified extension to HTTP/1.1.

> and i thought PUT and DELETE were basically dead.. atleast, in hopes of browsers being able to use them.

Browsers can use PUT and DELETE.

HTML Forms however, support only the post and get methods. (I don't really get why: the semantics as form methods for PUT, PATCH, and DELETE as form methods seem pretty obvious given those of GET and POST.)

[fizzbatter]

Ah yea, i'm referring to HTML Forms specifically. Thanks for the correction