Re:Dropbox starts using POST, and why this is poor API design
by hcarvalhoalves on Monday March 02, 2015 @05:05PM
(#9134653)
His alternative approach is actually pretty clever, even if not the best for Dropbox's API. I can see a number of advantages.
If the query result is it's own resource, you get async for free (the POST can return the URI it will be at before it's ready), the server can cache the result indefinitely if wanted, and the client can treat the API as an immutable dataset.
If the query result is it's own resource, you get async for free (the POST can return the URI it will be at before it's ready), the server can cache the result indefinitely if wanted, and the client can treat the API as an immutable dataset.