On 11/28/06, Steve Jones <[EMAIL PROTECTED]> wrote: > Not from the perspective of the consumer, when I see a URI that > includes something like "drawGraph?xData=fred&yData=pointless" then > I'm calling drawGraph with those parameters.
And if the publisher of the *same* functionality used this instead; http://example.org/kdjfalkjdfnawkflaudfnakjsdnfalufh then what would the operation be there? > I don't care whether its "GET" or whatever, its drawGraph that I am > calling. In the same way as when I call www.google.com/analytics I am > calling analytics not "GET". This is one of the things I like about > REST in that it explicitly encodes the method within the URI making it > simpler to read directly in the code (as opposed to in tools as with > WS, which I also like), at no stage ever when I'm using REST things am > I thinking "GET", I'm thinking about what the URI describes. No Steve, REST doesn't encode the method within the URI. With all due respect, that statement shows me that you don't yet understand it. REST is an architectural style. It has constraints that you have to follow in order to realize its benefits. One of these constraints is that operations be uniform. On the Web, that means in effect, that the operation has to be an HTTP operation (or an extension therefore, e.g. WebDAV). Mark.
