[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: What does SOAP really add?

• To: "Didier PH Martin" <martind@n...>,"Adam Turoff" <ziggy@p...>,"Michael Kay" <michael.h.kay@n...>
• Subject: RE: What does SOAP really add?
• From: "Joshua Allen" <joshuaa@m...>
• Date: Tue, 23 Apr 2002 11:09:51 -0700
• Cc: <xml-dev@l...>
• Thread-index: AcHq5bFncj1cwMzXQ/uaiFfsaMuAlQACz3iQ
• Thread-topic: What does SOAP really add?

> There are more ways to fetch a document then using an HTTP GET (confirmed
> by the millions of documents produced that way).

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.

Whether it is the fault of the client for being naïve, the fault of the service for requiring sophistication, or the fault of neither due to such usages being out of scope of the design of the service is a matter for endless debate.

(Replace naïve/sophistication with facist/flexibility above if you want to make the argument that XSLT is deliberately naïve in order to enforce RESTful architectures). 

• Follow-Ups:
  • Re: What does SOAP really add?
    • From: Adam Turoff <ziggy@p...>
  • Re: What does SOAP really add?
    • From: Mark Baker <distobj@a...>

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