W3C home > Mailing lists > Public > public-ws-async-tf@w3.org > April 2005

NEW ISSUE: Support for asynchronous / multi-MEP usage of web services

From: Glen Daniels <gdaniels@sonicsoftware.com>
Date: Thu, 14 Apr 2005 18:56:52 -0400
Message-ID: <80A43FC052CE3949A327527DCD5D6B27F9B4F9@MAIL01.bedford.progress.com>
To: <public-ws-async-tf@w3.org>, <public-ws-addressing@w3.org>

Title: Support for asynchronous / multi-MEP usage of web services


This issue serves as a placeholder for the stuff falling into the
"async" bag.  How do we correctly and interoperably specify the behavior
for callbacks, asynch responses, etc. over multiple transports in a
consistent way?  How do the various layers of MEPs (application, WSDL,
SOAP) bind to each other?  Etc.


Our charter indicates that we must specify how the MAPs are to be used
in order to achieve asynchrony with all WSDL 1.1 and 2.0 MEPs.  At
present there is no interoperable way to do this, partially due to
limitations or omissions which exist in the current SOAP and WSDL specs.
In order for the WS-Addressing group to declare victory (and build a
functional test suite), these limitations/omissions must be remedied,
and WS-Addressing must also appropriately adapt (if necessary) to
support these patterns.

Proposal to move forward:

This issue is now being dealt with in the large by the Async TF [1],
which any member of WSDL/WS-Addressing/XMLP may join.  The task force
has already presented several questions to the WGs, and hopes to bring a
set of concrete proposals/recommendations to the floor for consideration
in the coming weeks.


[1] http://lists.w3.org/Archives/Public/public-ws-async-tf/
Received on Thursday, 14 April 2005 22:56:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:48:42 UTC