Comments on: GET and POST aren’t verbs http://www.marcdegraauw.com/2007/06/05/get-and-post-arent-verbs/ Some thoughts on meaning, the web and everything Wed, 20 Aug 2008 18:33:25 +0000 http://wordpress.org/?v=2.2.2 By: Daniel Silva http://www.marcdegraauw.com/2007/06/05/get-and-post-arent-verbs/#comment-2530 Daniel Silva Tue, 31 Jul 2007 23:34:03 +0000 http://www.marcdegraauw.com/2007/06/05/get-and-post-arent-verbs/#comment-2530 (The form validator messed with the fake URL I was using in the example) I forgot to mention that the "actions" resource would be the list of actions the cat does: walk, talk, whines, etc. (The form validator messed with the fake URL I was using in the example)

I forgot to mention that the “actions” resource would be the list of actions the cat does: walk, talk, whines, etc.

]]> By: Daniel Silva http://www.marcdegraauw.com/2007/06/05/get-and-post-arent-verbs/#comment-2529 Daniel Silva Tue, 31 Jul 2007 23:31:10 +0000 http://www.marcdegraauw.com/2007/06/05/get-and-post-arent-verbs/#comment-2529 Hello. I just want to comment on your cat example. If you consider "cat" your resource, then GET, POST, PUT and DELETE (GPPD, for short) make sense. Your cat resource can be composed of many other resources, like for instance "actions". Then, your URI http:///cat/actions could answer to GPPD calls and manage the actions that the cat resource is associated with. My point is that with some effort, you can model many things as Resources, it's a matter of finding the right abstractions, I suppose. Hello.

I just want to comment on your cat example.

If you consider “cat” your resource, then GET, POST, PUT and DELETE (GPPD, for short) make sense. Your cat resource can be composed of many other resources, like for instance “actions”.

Then, your URI http:///cat/actions could answer to GPPD calls and manage the actions that the cat resource is associated with.

My point is that with some effort, you can model many things as Resources, it’s a matter of finding the right abstractions, I suppose.

]]> By: Lars Marius Garshol http://www.marcdegraauw.com/2007/06/05/get-and-post-arent-verbs/#comment-1628 Lars Marius Garshol Thu, 07 Jun 2007 20:24:33 +0000 http://www.marcdegraauw.com/2007/06/05/get-and-post-arent-verbs/#comment-1628 > The problem is, this is not how the current Web works. I couldn't agree more. When RESTafarians claim that REST obviously works because the web works so well they are missing the point, because, as you say, the current web doesn't use REST. So there isn't really just a choice between SOAP and REST. The choice is really SOAP, REST, or plain HTTP. When we made the TMRAP Topic Maps "protocol" we gave it a SOAP interpretation and a plain HTTP interpretation. The latter was not REST by any stretch of the imagination, but it was exactly the way the current web works. Of course, you could claim that REST is better, and for many situations it's true that REST is very clean, but it's not always convenient to make your web protocol RESTy. > The problem is, this is not how the current Web works.

I couldn’t agree more. When RESTafarians claim that REST obviously works because the web works so well they are missing the point, because, as you say, the current web doesn’t use REST.

So there isn’t really just a choice between SOAP and REST. The choice is really SOAP, REST, or plain HTTP. When we made the TMRAP Topic Maps “protocol” we gave it a SOAP interpretation and a plain HTTP interpretation. The latter was not REST by any stretch of the imagination, but it was exactly the way the current web works.

Of course, you could claim that REST is better, and for many situations it’s true that REST is very clean, but it’s not always convenient to make your web protocol RESTy.

]]>