Re: SOAP binding to HTTP

The SOAPaction requirement has been removed in SOAP 1.2 and replaced by
a non-transport-specific mechanism (see
http://www.w3.org/TR/2002/CR-soap12-part2-20021219/#ietf-action).

> -----Original Message-----
> From: Discussion of implementing SOAP applications today
> [mailto:[email protected]] On Behalf Of Dean, Michael D.
> Sent: Thursday, April 17, 2003 12:22 PM
> To: [email protected]
> Subject: [SOAP] SOAP binding to HTTP
> Importance: Low
>
>
> It seems to me that the binding between SOAP and HTTP is unnecessarily
> "coupled" due to the specification of a SOAP-specific HTTP
> Header (SOAP
> ACTION:)...wouldn't the ideal situation be that a particular
> value or value
> structure to an standard HTTP header would serve adequately?
> What are the
> reasons for a SOAP-specific HTTP header?
>
> > Best Regards,
> >
> > Michael Dean
> > Sun Certified Programmer for the Java 2 Platform
> > Washington State Department of Corrections
> > 360-664-8802
> > mailto:[email protected]
> >
> >  "Instead of always harping on a man's faults,
> >          tell him of his virtues.
> >   Try to pull him out of his rut of bad habits."
> >                        - Pollyanna
> >
> >
>