Signs you're veering from good API design(blog.apiaxle.com)
blog.apiaxle.com
Signs you're veering from good API design
http://blog.apiaxle.com/post/signs-youre-veering-from-good-api-design
http://blog.apiaxle.com/post/signs-youre-veering-from-good-api-design
> I am getting frustrated by the number of people calling any HTTP-based interface a REST API.
If REST is to mean something useful then it should mean more than following the HTTP protocol.
This stuff from the article is in the HTTP spec:
> People have a tendency to route everything, including non-safe operations, through a GET.
The Http Spec http://tools.ietf.org/html/rfc2616#section-9.1:
> In particular, the convention has been established that the GET and HEAD methods SHOULD NOT have the significance of taking an action other than retrieval. These methods ought to be considered "safe".
I don't think "REST == Good" for all API's. In 2014! I think people who want to tell us about REST should know Fielding said.