Comments on: Difficulty PUTting up with REST http://parand.com/say/index.php/2005/12/27/difficulty-putting-up-with-rest/ Parand Tony Darugar: A Cruel and Petty Dictator Tue, 17 Jan 2012 23:10:42 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Crash course in sane Web programming http://parand.com/say/index.php/2005/12/27/difficulty-putting-up-with-rest/comment-page-1/#comment-43605 Crash course in sane Web programming Tue, 13 Mar 2007 02:21:38 +0000 http://www.parand.com/say/index.php/2005/12/27/difficulty-putting-up-with-rest/#comment-43605 [...] As to why this might not work, see what Parand had to say about it. [...] [...] As to why this might not work, see what Parand had to say about it. [...]

]]> By: Chris Radcliff http://parand.com/say/index.php/2005/12/27/difficulty-putting-up-with-rest/comment-page-1/#comment-2221 Chris Radcliff Wed, 28 Dec 2005 18:49:37 +0000 http://www.parand.com/say/index.php/2005/12/27/difficulty-putting-up-with-rest/#comment-2221 I'm right there with you. We went through the same process when deciding how to do the EVDB API (http://api.evdb.com/docs). We ended up going with a RESTful but not RESTafarian implementation, basically adding the verb to the URL instead of using HTTP actions as verbs, plus removing the object ID from the URL and shifting it to the query string. Thus: http://host/rest/noun(s)/verb?id=ID e.g. http://api.evdb.com/rest/users/locales/list?id=chris_radcliff I'm sure there was some ideologically pure way of constructing all of our methods using HTTP verbs, but we made the decision to do it this way in order to make it easier for us to develop, test, and explain. We're still getting all the benefits of REST, as far as we can tell. I’m right there with you. We went through the same process when deciding how to do the EVDB API (http://api.evdb.com/docs). We ended up going with a RESTful but not RESTafarian implementation, basically adding the verb to the URL instead of using HTTP actions as verbs, plus removing the object ID from the URL and shifting it to the query string. Thus:

http://host/rest/noun(s)/verb?id=ID
e.g. http://api.evdb.com/rest/users/locales/list?id=chris_radcliff

I’m sure there was some ideologically pure way of constructing all of our methods using HTTP verbs, but we made the decision to do it this way in order to make it easier for us to develop, test, and explain. We’re still getting all the benefits of REST, as far as we can tell.

]]> By: Mark Baker http://parand.com/say/index.php/2005/12/27/difficulty-putting-up-with-rest/comment-page-1/#comment-2213 Mark Baker Wed, 28 Dec 2005 05:16:52 +0000 http://www.parand.com/say/index.php/2005/12/27/difficulty-putting-up-with-rest/#comment-2213 "Did I get that right? Isn’t that very not REST?" Yup. This is a pretty common bug in many web app frameworks. CGI does it (unless you know to look for the method). Zope does it. Ruby on rails does (did) it. Others too... As for recommendations re PUT, see; http://www.intertwingly.net/wiki/pie/PutDeleteSupport http://www.intertwingly.net/wiki/pie/CarrotVsOrange “Did I get that right? Isn’t that very not REST?”

Yup. This is a pretty common bug in many web app frameworks. CGI does it (unless you know to look for the method). Zope does it. Ruby on rails does (did) it. Others too…

As for recommendations re PUT, see;

http://www.intertwingly.net/wiki/pie/PutDeleteSupport
http://www.intertwingly.net/wiki/pie/CarrotVsOrange

]]>