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 09:15:42 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D0297CDCB@red-msg-07.redmond.corp.microsoft.com>
To: "Williams, Stuart" <skw@hplb.hpl.hp.com>, "Mark Nottingham" <mnot@mnot.net>
Cc: <xml-dist-app@w3.org>

>>It would be interesting to hear. My intuition (and experience, FWIW) 
>>is that applications will be designed to take advantage of the most
>>transport, and specify which binding is in use.

I absolutely agree with this.

>So is SOAP really a protocol or is it yet another 
>packaging/encapsulation format?

...as opposed to yet another protocol ;? Protocols are used for all kind
of purposes and exhibit all kind of properties and diving into what
constitutes a protocol and how they can be classified is nothing less
than a PhD subject.

The discussion that we have had about the SOAP processing model will
tell you that there is more than merely a wrapper - there is in fact a
processing model that defines how to deal properly with SOAP messages
and when to generate faults.

It is true that SOAP by itself doesn't define many of the application
layer characteristics that most other application protocols exhibit such
as message exchange patterns, routing, correlation, etc. The reason
being that I think we believe we have a good extensibility mechanism
that allows us to add such features. Time will tell whether this is a
valid assumption.

Received on Friday, 6 July 2001 12:41:07 UTC

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