News for hackers. Stuff that matters.
Re:A preview of the new Dropbox API v2 by smarx on Wednesday April 08, 2015 @02:21PM (#9342741)
Is there some benefit to implementing it as a GET instead?
Re:A preview of the new Dropbox API v2 by Revell on Wednesday April 08, 2015 @04:17PM (#9343618)
Caching for one. I just don't see a reason for moving as much as possible to POST since this seems to go against what the different methods (GET, HEAD, POST, PUT, DELETE, etc) were meant for.
Re:A preview of the new Dropbox API v2 by dragonwriter on Wednesday April 08, 2015 @04:22PM (#9343661)
> I just don't see a reason for moving as much as possible to POST since this seems to go against what the different methods (GET, HEAD, POST, PUT, DELETE, etc) were meant for.

Arguably, HTTP-based RPC with consistent use of POST is a lot more straightforward of a model than the kinda-sorta-REST-without-HATEOAS that a lot of APIs use, and arguably for APIs whose scope is a particular server and not the kind of generality that the web as a whole itself (the archetypical REST service) provides, POST-based HTTP-RPC is a more natural choice than REST.

Re:A preview of the new Dropbox API v2 by smarx on Wednesday April 08, 2015 @05:27PM (#9344112)
The new API does support GET for requests that are cacheable (e.g. fetching a file or thumbnail).

The RPC-style endpoints all use POST and are not cacheable.

Re:A preview of the new Dropbox API v2 by untog on Wednesday April 08, 2015 @06:21PM (#9344491)
It helps to clarify what will happen. GET requests should never alter the data in the backend, wheras PUT, POST and DELETE would.
Re:A preview of the new Dropbox API v2 by mmastrac on Wednesday April 08, 2015 @02:49PM (#9342925)
If it's an unauthenticated call you can use a browser, but if all the calls require a header like that, I don't see a reason to.