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: Mon, 7 May 2001 14:50:37 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D0297CBE9@red-msg-07.redmond.corp.microsoft.com>
To: <moore@cs.utk.edu>, "Mark Nottingham" <mnot@akamai.com>
Cc: <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".

The difference is that one is a destination which is carried in HTTP by
the request-URI but the other is a hint about what is in the message.
This is why SOAPAction is a separate parameter.


>> On Sun, May 06, 2001 at 03:12:08PM -0400, Keith Moore wrote:
>> > and client APIs.  It also keeps HTTP servers from having to know 
>> > specifically whether a particular URI corresponds with a SOAP 
>> > request (in which case it might have to look at the SOAPAction 
>> > header in order to know how to handle it) or not (in which case the

>> > SOAPAction header should be ignored).
>> Yep; seems to me that Content-Type ss more appropriate for dispatch, 
>> if doing it in a header is desireable.
>ugh.  only if you must.  the URL is *far* better for this purpose.
Received on Monday, 7 May 2001 18:52:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:13 UTC