W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2002

Re: Issue 133, and permitting no body

From: Mark Baker <distobj@acm.org>
Date: Mon, 4 Feb 2002 18:09:28 -0500 (EST)
Message-Id: <200202042309.SAA29036@markbaker.ca>
To: Mike.Champion@SoftwareAG-USA.com (Champion, Mike)
Cc: xml-dist-app@w3.org
> Hmmm ... I hate to dive into shark-infested waters, but I thought of SOAP as
> the application coordination protocol and HTTP just one of the transports.
> HTTP itself is much more than a transport protocol, but the SOAP RPC binding
> is only using it as a way to transport messages.  One COULD use SOAP-format
> messages in a REST-way -- using GET, PUT, POST as appropriate, but that's
> not RPC ???

That's a nomenclature issue, I guess.  GET, PUT, POST, DELETE can be
considered RPC methods as well as "getStockQuote" can.  But what most
developers think of as "RPC" is that they get to define their own
methods.

MB
-- 
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@planetfred.com
http://www.markbaker.ca   http://www.planetfred.com
Received on Monday, 4 February 2002 18:07:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:06 GMT