W3C home > Mailing lists > Public > xml-dist-app@w3.org > May 2001

Re: SOAP/XML Protocol and filtering, etc.

From: Keith Moore <moore@cs.utk.edu>
Date: Tue, 08 May 2001 01:31:19 -0400
Message-Id: <200105080531.BAA26294@astro.cs.utk.edu>
To: "Henrik Frystyk Nielsen" <henrikn@microsoft.com>
cc: "Keith Moore" <moore@cs.utk.edu>, "Mark Nottingham" <mnot@akamai.com>, ietf@ietf.org, xml-dist-app@w3.org
> >> The meaning of SOAPAction is not to say that "this is a stockquote
> >> service" but to say that "I am sending you a SOAP message of a type
> >> that is part of a stock quote service".
> >
> >okay, fine.  but why bother exposing this in the request header at all?
> 
> Because it can be hard to deduce from the message - especially as
> messages may be composed of many pieces from other places using SOAP's
> modular extensibility mechanism (headers). In a sense this is similar to
> that a media type can be hard to guess based on the entity alone.

then add that to the SOAP payload that gets passed in the HTTP entity
body.  don't penalize HTTP for SOAP's design deficiencies.

Keith
Received on Tuesday, 8 May 2001 01:31:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:01 GMT