> There are models for this in XML-RPC already (Yes, that's
XML RPC,
but it's still applicable, I think).
Mark,
you should read an introductory text on REST :) I recommend some of
Fielding's writings, for example this one:
http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
I am just learning, thanks for the reference. So far I've been working with the two
O'Reilly books: RESTful Web Services and Cookbook.
REST is not RPC, on purpose. A POST on a collection has well-defined
semantics: it should create a new resource inside the collection. So
when POSTing to the "hosts" collection, the right semantics is that it
should create a new host.
OK, I see that. I've also been reading (repeatedly) the RHEVM REST API spec and
I'm making connections I'd missed with respect to how actions are presented and
used. I'm coming around.
Resource R presents a set of actions as a list of resource references R/{actionname}. Any
questions you have then about the actions should be answered by GET queries to those
resources.
Got it. I'm ready to move on... Now, about those parameters...
- Mark