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

RE: XML Protocol: Proposals to address SOAPAction header

From: Eamon O'Tuathail <eamon.otuathail@clipcode.com>
Date: Mon, 11 Jun 2001 20:34:07 +0100
To: <xml-dist-app@w3.org>
Message-ID: <NCBBIFBIECFPOABMKKBDIEPDDMAA.eamon.otuathail@clipcode.com>
>> First, what is a transport binding?  What information can be carried
>> there, which bits can the SOAP processor itself (or applications built
>> on top) utilize to access extra functionality or optimize things (for
>> example, the implicit correlation provided by an HTTP binding), etc.

The discussion seems to be evolving into "how do we perform routing of SOAP
messages, when we have more than two peers, and they are not all using the
same underlying application protocol?"

One option is to start mixing up our bindings (e.g. carry HTTP info in other
bindings), which seems to me to be a non-starter. Surely a better option
would be to define routing using SOAP.

The Microsoft guys have proposed a SOAP Routing Protocol (SOAP-RP -
http://www.gotdotnet.com/team/xml_wsspecs/soap-rp/default.html), which apart
from the friendly copyright notice of top, seems to me to be a very sensible
idea. Are there any other SOAP routing proposals out there?
Received on Monday, 11 June 2001 15:31:41 GMT

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