• To: julian.reschke@g... (Julian Reschke)
• Subject: Re: What does SOAP really add?
• From: John Cowan <jcowan@r...>
• Date: Tue, 23 Apr 2002 10:44:18 -0400 (EDT)
• Cc: martind@n... (Didier PH Martin), xml-dev@l...
• In-reply-to: <JIEGINCHMLABHJBIGKBCKEGAEHAA.julian.reschke@g...> from "Julian Reschke" at Apr 23, 2002 04:17:57 PM

Julian Reschke scripsit:

> HTTP GET is supposed to be a side-effect free operation. HTTP POST isn't.

Just so.

> I think the TAG would argue that if you have a POST operation which is
> side-effect free, you should have made it a GET in the first place.

I think that overstates the case.   URLs can in practice only be so
long, and a side-effect-free operation might require a large number of
parameters.  So POSTs can be side-effect-free, but GETs should never
have side effects.

-- 
John Cowan <jcowan@r...>     http://www.reutershealth.com
I amar prestar aen, han mathon ne nen,    http://www.ccil.org/~cowan
han mathon ne chae, a han noston ne 'wilith.  --Galadriel, _LOTR:FOTR_

• References:
  • RE: What does SOAP really add?
    • From: "Julian Reschke" <julian.reschke@g...>

• 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