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

RE: SOAP/XML Protocol and filtering, etc.

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Tue, 8 May 2001 07:27:32 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D0344179A@red-msg-07.redmond.corp.microsoft.com>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: "Mark Nottingham" <mnot@akamai.com>, <ietf@ietf.org>, <xml-dist-app@w3.org>

>> 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.

It is not for the benefit of SOAP - it is for the benefit of HTTP which
is why it is expressed in a manner that is digestible by HTTP. Your
argument could equally well be applied to media types so does that mean
that you feel the same way about that?

Henrik
Received on Tuesday, 8 May 2001 10:54:47 GMT

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