W3C home > Mailing lists > Public > www-ws@w3.org > July 2001

RE: open transport protocol for aysnc web services?

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Fri, 13 Jul 2001 11:52:39 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D03441D02@red-msg-07.redmond.corp.microsoft.com>
To: "john d. beatty" <jbeatty@gonesilent.com>, <www-ws@w3.org>

>IMO, there is a serious need for a generic, standard asynch 
>messaging protocol that allows any type of message to be 
>routed.  SOAP-RP tightly couples the message routing 
>information to the message (e.g., the message routing 
>information is contained in the header of the SOAP message), 
>thus it is not a generic solution (only SOAP messages are 
>allowed).  APEX, on the other hand, allows arbritary messages.

SOAP-RP does inherently support intermediaries that can play a variety
of different roles extending to much more than simply routing. While the
SOAP protocol language itself is XML you can indeed support arbitrary
data using DIME.

>It might be a good thing for the SOAP community to clamor for 
>a more generic messaging solution than SOAP-RP and for to put 
>pressure on Microsoft, IBM, Sun, TIBCO, webMethods, et. al. to 
>try a little harder on a standard, generic asynch messaging protocol.

SOAP-RP supports a variety of underlying protocols, an open-ended set of
message exchange patterns, async messaging, and symmetric as well as
asymmetric message paths between peers. That seems pretty flexible to
me.

Henrik
Received on Friday, 13 July 2001 14:54:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:38 GMT