News for hackers. Stuff that matters.
Re:Dropbox starts using POST, and why this is poor API design by treve on Monday March 02, 2015 @06:44PM (#9135191)
I think the main problem people have with this, is that REST is not necessarily easy. And easy sometimes wins over 'good'.
Re:Dropbox starts using POST, and why this is poor API design by cauterized on Monday March 02, 2015 @07:05PM (#9135318)
Strict REST can also result in a lot more requests than a denormalized API might, and that's mobile-unfriendly.
Re:Dropbox starts using POST, and why this is poor API design by dragonwriter on Monday March 02, 2015 @07:30PM (#9135401)
Strict REST doesn't require normalization; there is nothing in the definition of the REST architectural style that prohibits resources that are aggregates of -- in DB terms, equivalent to whole tables, or rows from a complex view, or whole complex views -- of other resources, and allowing those derived resources to be directly retrieved or manipulated (with the latter also affecting the "base" resources.)

The kind of REST that simply maps resources to DB rows with collection resources for base tables and does nothing else is naïve REST, not particularly any stricter REST than more complex and application-suited resource models.

Re:Dropbox starts using POST, and why this is poor API design by dyoder on Monday March 02, 2015 @06:50PM (#9135232)
you're absolutely right. and i'd be fine with that if the objection was just that: this is too hard to implement, or we don't have time, and so on. it's the rationalizing that's annoying. and obviously DropBox has the resources to implement whatever design they choose.