I'm collecting popular misconceptions about REST. Got some of your own? Please let me know using #notrest. I'll follow up with a few.

Feb 27, 2013 · 3:34 PM UTC

28
9
4
Load newest
Replying to @stilkov
@stilkov Every action with a resource should be communicated through the URL path. #notrest
Replying to @stilkov
@stilkov that having performed one HTTP method against a URL, others verbs would also be supported and magically do the right thing #notREST
Replying to @stilkov
@stilkov take some code, plug in a REST library, and hey presto you have a web service #notrest
Replying to @stilkov
@stilkov REST because using JSON over HTTP is faster and easier than XML over SOAP - true dat, but #notrest
Replying to @stilkov
Resources of the REST API need to reflect the entities and relations as defined by the relational model or domain model. #notrest
Replying to @stilkov
@stilkov nitter.vloup.ch/shit_so_says/sta… #notrest
Shit SO says @shit_so_says
13 Jan 2013
REST is using the various HTTP methods (mainly GET/PUT/DELETE) to manipulate data.
Replying to @stilkov
@stilkov nitter.vloup.ch/shit_so_says/sta… #notrest
Shit SO says @shit_so_says
31 Jan 2013
RESTful is another buzz-word that popped out of the Web 2.0 erection.
Replying to @stilkov
@stilkov or the minimalistic view that assumes things REST enough if the service can be called from a browser with a XHRequest #notrest
1
Replying to @stilkov
@stilkov REST is for web applications only. #notrest
1
1
Replying to @stilkov
@stilkov That RESTfullness is an analog quality, so phrases like "more RESTful" or "pure REST" are not tautologies. #notrest #almostpregnant
1
1
Load more