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

RE: What does SOAP really add?

• To: "Mark Baker" <distobj@a...>,"Francis Norton" <francis@r...>
• Subject: RE: What does SOAP really add?
• From: "Joshua Allen" <joshuaa@m...>
• Date: Tue, 23 Apr 2002 11:40:07 -0700
• Cc: "Julian Reschke" <julian.reschke@g...>,"Didier PH Martin" <martind@n...>,Bill de hÓra <dehora@e...>,<xml-dev@l...>
• Thread-index: AcHq50VrpjlUfa78SHu+7eef/98bhgADTejQ
• Thread-topic: What does SOAP really add?

> Well, that's the whole point of this discussion.  POST should not be
> used to "fetch results", because we already have a method that does
> that; GET.  If you have more than one method that means "fetch stuff",

We all agree that POST is almost never used in the "proper" way that you describe above.  You are making an argument about what *should* be.  I believe the original argument was trying to make some claims about current *reality* (that XSLT was supposedly incompatible with SOAP).  In the end, the only part of that reality claim that ended up being true is that "GET is not able to retrieve results of a POST".  This is tautological, and has nothing to do with either SOAP or XSLT.

I personally *agree* that POST should not be used to "fetch results".  I am simply pointing out that the original SOAP & XSLT argument was really just the POST & GET argument in drag, and cloaking it as a "practical, my stuff today breaks because of SOAP" problem was disingenuous.  That doesn't make me anti-idempot.

• 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