Re: A viewpoint on harvesting REST

Providing an web service RPC 'ease of use' client binding for GET and 
POST HTTP messages is fairly easy to do. Soap 1.2 is already doing this 
for GETs that return Soap messages.

SOAP is a messaging technology with RPC layered over it as a style. With 
the doc literal binding, client tools already have to 'dig' to present 
an RPC view of what amounts to generic XML fragment.

RPC as a web service style will not be lost if web services is expanded 
to support the existing web.

Hao He wrote:
> A conclusion:
> 
> There is no technical reason why Soap cannot embrace and extend the 
> existing web. It should; and, WSAWG should reinforce its commitment to 
> this goal.
> 
> <hh>There is a fundamental difference here between RPC (SOAP/WSDL is biased
> towards RPC) and REST. With RPC, state is internal and semantics are
> embedded in various method names and arguments.  With REST, state is
> external (can be GET) and semantics are carried by URIs and their
> representations. (The verb-vs-noun arguments.) Unless there is a
> reconciliation between those two, the gap is quite wide. A simple solution
> might be giving up RPC in SOAP/WSDL altogether but lots of people will cry.
> </hh>
> 
> Hao  
> 
> 
> ------------------------------------------------------------------------
> 
> =====================================================================
> WARNING -This e-mail, including any attachments, is for the 
> personal use of the recipient(s) only.
> Republication and re-dissemination, including posting to news 
> groups or web pages, is strictly prohibited without the express
> prior consent of
> Thomson Legal & Regulatory Limited
> ABN 64 058 914 668
> =====================================================================

Received on Wednesday, 31 July 2002 05:07:30 UTC