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

RE: Protocol Bindings

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Fri, 6 Jul 2001 08:24:21 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D0297CDC9@red-msg-07.redmond.corp.microsoft.com>
To: "Williams, Stuart" <skw@hplb.hpl.hp.com>
Cc: <xml-dist-app@w3.org>

>> What you state here is different from what you stated in the previous

>> mail. Either the "purpose of an XML Protocol Binding is to provide 
>> rules for the transfer of XML Protocol messages over some specific 
>> underlying protocol" or "the purpose of a protocol binding IS to 
>> describe how to make use of a particular underlying protocol to 
>> transfer XMLP/SOAP messages."
>Personally I think that both formulations say the same thing. 
>If the second communicates my intend more clearly to you, that's great.

There is a very big difference--it is not just a formulation problem and
we must have agreement on which one before we can effectively talk about
what bindings can do and cannot do. From an architectural consistency
point of view I don't think we have a choice but to use the latter.

When you say that SOAP or the SOAP binding defines the *transfer* then
what you are saying is that SOAP does routing - in order for SOAP to
transfer a message it has to know where it is going. The reason why I
keep saying that SOAP doesn't do routing is that some routing (or
endpoint identification) mechanism is necessary in order to transfer
messages but SOAP doesn't define that and neither does the binding.

The binding is exactly what it sounds like - a gluing mechanism between
SOAP and whatever underlying protocol. There should be no additional
semantics defined by the binding because the places where we add
semantics is either as SOAP extensions or as underlying protocols.
Semantics defined by the binding is not defined as part of underlying
protocols and not defined within the extensibility mechanism of SOAP. In
other words we have no good way to talk about it in terms of processing
model, extensibility model etc. 

Received on Friday, 6 July 2001 11:49:48 UTC

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