• To: "Mark Baker" <distobj@a...>, "Joshua Allen" <joshuaa@m...>
• Subject: Re: What does SOAP really add?
• From: "Didier PH Martin" <martind@n...>
• Date: Tue, 23 Apr 2002 14:47:43 -0400
• Cc: "Adam Turoff" <ziggy@p...>, "Michael Kay" <michael.h.kay@n...>, <xml-dev@l...>
• References: <4F4182C71C1FDD4BA0937A7EB7B8B4C104F05729@r...> <20020423142750.N6973@w...>

Hi Mark,

Mark said:
> You can't easily use POST to retrieve stuff, because;
>
> - all "stuff" needs a URI to identify it, and
> - you shouldn't have to know any "secret incantation" to put in the POST
> body to get that resource to respond.

Didier replies:
OK Mark if we stick to using solely the HTTP GET method then we need to
create a URI sufficiently flexible to allow the formulation of rich queries.
URLs are a complete breakdown on this matter.

This will be a necessary and sufficient condition to offer a good
alternative to the actual practice to use the HTTP POST method as a document
fetch invocation.

cheers
Didier PH Martin

• Follow-Ups:
  • Re: What does SOAP really add?
    • From: Francis Norton <francis@r...>

• References:
  • RE: What does SOAP really add?
    • From: "Joshua Allen" <joshuaa@m...>
  • Re: What does SOAP really add?
    • From: Mark Baker <distobj@a...>

• Prev by Date: Re: What does SOAP really add?
• Next by Date: RE: What does SOAP really add?
• Previous by thread: Re: What does SOAP really add?
• Next by thread: Re: What does SOAP really add?
• Index(es):
  • Date
  • Thread