- From: Keith Moore <moore@cs.utk.edu>
- Date: Tue, 08 May 2001 01:24:09 -0400
- To: "Dick Brooks" <dick@8760.com>
- cc: "Keith Moore" <moore@cs.utk.edu>, "Henrik Frystyk Nielsen" <henrikn@microsoft.com>, "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. HTTP servers do not dispatch on content-type. either you're dispatching on the URI or you're breaking compatibility with HTTP. Keith
Received on Tuesday, 8 May 2001 01:24:22 UTC