Hey Pete, On 6/5/07, Peter Lacey <[EMAIL PROTECTED]> wrote: > The ECS (E-Commerce Service) "REST" API specifies a single URL: > > http://ecs.amazonaws.com/onca/xml?Service=AWSECommerceService > > onto which are tacked the operation name and various parameters. Now, > as Sam Ruby recently pointed out, this is not a surefire guarantee that > the application is not RESTful, but if GETting one of those URIs changes > server side state, then they are not RESTful.
That's actually not the case. That the server changes state as a result of GET matters not to the RESTfulness of the system. > In Amazon's case, there > are URI-based operations to create a remote shopping cart, add items to > the cart, and update items in the cart. Thus ECS does not have a > uniform interface -- everything is tunneled over GET (or POST); is not > cacheable; does not have self-descriptive messages; does not manipulate > state via representations; and, in the case of using POST instead of > GET, does not have identifiable resources, You're right, I forgot that about that. It's been some years since I've looked at them. > For EC2 (the Elastic Compute Cloud) it's the same thing. In fact, > Amazon calls the EC2 REST-RPC hybrid interface the "Query API" and > promises a true REST API sometime in the future. > http://docs.amazonwebservices.com/AmazonEC2/dg/2007-01-19/TechnicalFAQ.html#d0e15107 I haven't looked at EC2. Mark.
