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

RE: SOAP/XML Protocol and filtering, etc.

From: Dick Brooks <dick@8760.com>
Date: Mon, 7 May 2001 20:13:14 -0500
To: "Keith Moore" <moore@cs.utk.edu>, "Henrik Frystyk Nielsen" <henrikn@microsoft.com>
Cc: "Mark Nottingham" <mnot@akamai.com>, <ietf@ietf.org>, <xml-dist-app@w3.org>

SOAP messages can take many forms. SOAPAction provides the information
needed by a generic message broker to dispatch a message to the appropriate
handler, without requiring the message broker to have intimate knowledge of
each SOAP message structure. The SOAPAction can serve as a "key" into a
table of message processors. IMO, SOAPAction is conceptually similar to the
MIME Content-type.

If a generic message broker couldn't determine the message type from a
request header it require intimate knowledge of each message structure in
order to perform dispatch functions. It's more efficient and easier to write
message broker that operates off the MIME/HTTP headers for dispatching

Dick Brooks (ebXML liaison)

-----Original Message-----
From: xml-dist-app-request@w3.org [mailto:xml-dist-app-request@w3.org]On
Behalf Of Keith Moore
Sent: Monday, May 07, 2001 7:17 PM
To: Henrik Frystyk Nielsen
Cc: moore@cs.utk.edu; Mark Nottingham; ietf@ietf.org;
Subject: Re: SOAP/XML Protocol and filtering, etc.

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

Received on Monday, 7 May 2001 21:03:50 UTC

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