W3C home > Mailing lists > Public > www-ws-arch@w3.org > August 2003

RE: Issue: Synch/Asynch Web services

From: Ugo Corda <UCorda@SeeBeyond.com>
Date: Mon, 4 Aug 2003 13:53:57 -0700
Message-ID: <EDDE2977F3D216428E903370E3EBDDC908126A@MAIL01.stc.com>
To: <jdart@tibco.com>, <www-ws-arch@w3.org>

So my conclusion from these latest discussions is that not only we might have a problem in our definition of sync/async, but that the Web services community has a problem when it comes to defining actual standards for sync/async that guarantee interoperability (async being the real issue here).

To be honest, the latter problem is the one that concerns me most, even though it can be argued that it cannot be fixed until a proper definition of sync/async is provided. (I am personally not sure if this is in practice true - people have been doing sync/async Web services for quite a while, and usually they can easily tell a sync WS from an async one when they see it).

Ugo

> -----Original Message-----
> From: Jon Dart [mailto:jdart@tibco.com]
> Sent: Monday, August 04, 2003 1:26 PM
> To: Ugo Corda
> Cc: www-ws-arch@w3.org
> Subject: Re: Issue: Synch/Asynch Web services
> 
> 
> Ugo Corda wrote:
> 
> > But if Request-Response is dropped from the spec, then 
> evidently In-Out must work for both synchronous and 
> asynchronous behaviors, so the WSDL interface gives me no 
> clue of what the service expects.
> 
> Right, and also it doesn't tell you how to implement any kind of 
> asynchronous interaction in an interoperable fashion (which 
> must include 
> the correlation feature).
> 
> --Jon
> 
> 
> 
Received on Monday, 4 August 2003 16:54:09 GMT

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