• To: Joshua Allen <joshuaa@m...>
• Subject: Re: What does SOAP really add?
• From: Mark Baker <distobj@a...>
• Date: Tue, 23 Apr 2002 14:27:50 -0400
• Cc: Didier PH Martin <martind@n...>, Adam Turoff <ziggy@p...>, Michael Kay <michael.h.kay@n...>, xml-dev@l...
• In-reply-to: <4F4182C71C1FDD4BA0937A7EB7B8B4C104F05729@r...>; from joshuaa@m... on Tue, Apr 23, 2002 at 11:09:51AM -0700
• References: <4F4182C71C1FDD4BA0937A7EB7B8B4C104F05729@r...>

> Right.  Although I think that Paul's main point was that GET is the easiest method to implement, and there are lots of clients that can do GET but not POST.  Paul was attempting to make the argument that any system which uses a POST where a GET would suffice is shutting out these naïve clients.

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.

MB
-- 
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@p...
http://www.markbaker.ca   http://www.planetfred.com

• Follow-Ups:
  • Re: What does SOAP really add?
    • From: "Didier PH Martin" <martind@n...>

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

• 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