REST does not require a specific response. The original paper used specific verb as an example present in the wild, which has oft been misinterpreted as require

REST does not require a specific response. The original paper used specific verb as an example present in the wild, which has oft been misinterpreted as required usage. Formatted summary - http://www.ics.uci.edu/%7Efielding/pubs/dissertation/rest_arch_style.htm http://www.ics.uci.edu/%7Efielding/pubs/dissertation/rest_ar... - "The most frequent form of request semantics is that of retrieving a representation of a resource (e.g., the "GET" method in HTTP), which can often be cached for later reuse." A critique of HTTP REST - http://cafe.elharo.com/web/why-rest-failed/ http://cafe.elharo.com/web/why-rest-failed/ - "Representational State Transfer (REST) is the explicit architecture of HTTP and the World Wide Web" which is a notably incorrect statement. Other interesting articles: http://www.artima.com/lejava/articles/why_put_and_delete.html http://www.artima.com/lejava/articles/why_put_and_delete.htm... http://roy.gbiv.com/untangled/2009/it-is-okay-to-use-post http://roy.gbiv.com/untangled/2009/it-is-okay-to-use-post