• To: Mark Baker <distobj@a...>
• Subject: Re: Elliotte Rusty Harold on Web Services
• From: Rich Salz <rsalz@d...>
• Date: Fri, 31 Jan 2003 12:59:35 -0500
• Cc: "Cavnar-Johnson, John" <JCavnar-Johnson@s...>, xml-dev@l...
• In-reply-to: <20030131125153.G2173@w...>
• References: <003801c2c946$e5b34520$6401a8c0@cavnarjohnson> <3E3AAB07.4080403@d...> <20030131125153.G2173@w...>
• User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

> Consider these two examples;
> 
> POST some-uri HTTP/1.0
> Content-Type: application/xml
> [blank line]
> <number>3<number>
> 
> and
> 
> POST some-uri HTTP/1.0
> Content-Type: application/xml
> [blank line]
> <add>
> <number>3<number>
> </add>

In the first example, the action is implied by some-uri.  Your second 
example shows SOAP RPC, where the action is specified by an element. 
Your first example could be a SOAP "doc/literal" approach.

This isn't a REST issue.
	/r$

• References:
  • RE: Elliotte Rusty Harold on Web Services
    • From: "Cavnar-Johnson, John" <JCavnar-Johnson@s...>
  • Re: Elliotte Rusty Harold on Web Services
    • From: Rich Salz <rsalz@d...>
  • Re: Elliotte Rusty Harold on Web Services
    • From: Mark Baker <distobj@a...>

• Prev by Date: Re: Elliotte Rusty Harold on Web Services
• Next by Date: RE: Elliotte Rusty Harold on Web Services
• Previous by thread: Re: Elliotte Rusty Harold on Web Services
• Next by thread: RE: Elliotte Rusty Harold on Web Services
• Index(es):
  • Date
  • Thread