Alternative to SOAP, use http protocols for everything.
With four basic methods (GET, PUT, DELETE, POST) we could do what UDDI does with dozens of methods. REST is to web services what Reduced Instruction Set Computing (RISC) is to CPUs. But don't take the analogy too far: the costs and benefits are different in this context.
Sam Ruby, REST and SOAP : http://www.intertwingly.net/stories/2002/07/20/restSoap.html
Some best-practices : http://www.xml.com/pub/a/2004/08/11/rest.html
Semi-related. JonUdell on Rich Internet Applications and the URL as state :
Unlike a Web application which manages state information almost entirely on the server, though, an RIA achieves a more balanced distribution of that information between client and server. The benefits that flow from this arrangement can include responsiveness, context preservation, and offline capability. To achieve these benefits, though, we have to make some painful tradeoffs.
- RIAs are protocol-driven. A programmer who masters an application's protocols can extend it or combine it with other applications. But there are no integration hooks available to the user. In a Web application, those hooks are simply URLs. Consider what happens when you include a MapQuest URL in an email to someone. A piece of state information – namely, the state of the MapQuest viewer when displaying a given location – has been reduced to a token that one person can hand to another. The same thing can usefully apply to the state of a shopping cart, or an airline reservation.*
The idea that an application wears its state information on its sleeve, readily available for users to bookmark, modify, and trade, is an underappreciated strength of Web-based software.
(WarpLink) URL as state token to RDF's use of URIs for everything
See also :