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

RE: Async Web Services

From: Christopher B Ferris <chrisfer@us.ibm.com>
Date: Mon, 8 Jul 2002 11:14:18 -0400
To: "Naresh Agarwal" <nagarwal@in.firstrain.com>
Cc: "Krishna Sankar" <ksankar@cisco.com>, www-ws@w3.org
Message-ID: <OF0235C563.5D365A00-ON85256BF0.0052A9D9@rchland.ibm.com>

It isn't at all clear to me what is necessary in WSDL to "describe" a
MEP. I suppose that some of the defined properties might need to be exposed
(like reqres:role, reqres:immediateDestination URI and possibly web:method)
but it is my
understanding that the MEPs are intended to be "described" by means of a
specification such as that found in the SOAP1.2 Part 2 Adjuncts
specification [1] and [2].

Thus, WSDL shouldn't need much more than a means of identifying the MEP
in play for a given port by means of its assigned URI and any properties
that might



[1] http://www.w3.org/TR/2002/WD-soap12-part2-20020626/#singlereqrespmep
[2] http://www.w3.org/TR/2002/WD-soap12-part2-20020626/#soapresmep

                      "Naresh Agarwal"                                                                                            
                      <nagarwal@in.firs        To:       "Krishna Sankar" <ksankar@cisco.com>, <www-ws@w3.org>                    
                      train.com>               cc:                                                                                
                      Sent by:                 Subject:  RE: Async Web Services                                                   
                      07/08/2002 11:15                                                                                            

Hi Krishna,

>            If I am correct the only two modes of operation are fire and
> forget or req-response. Asynchronous web services or more precisely,
> stateful web services require some sort of correlation between
> invocations. ebXML has the conv id which could be used for this. Most
> probably the future web services interactions would be based
> on SOAP 1.2
> MEPs.

I agree that future Web Services interactions would be based on SOAP1.2
But is there *enough* support in WSDL1.1/WSDL1.2 to describe these MEPs?

Naresh Agarwal
Received on Monday, 8 July 2002 11:16:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:08 UTC