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

RE: Issue: Synch/Asynch Web services

From: Cutler, Roger (RogerCutler) <RogerCutler@chevrontexaco.com>
Date: Sat, 9 Aug 2003 13:47:16 -0500
Message-ID: <7FCB5A9F010AAE419A79A54B44F3718E026EFA4A@bocnte2k3.boc.chevrontexaco.net>
To: "Sai Surya Kiran Evani" <evani@informatik.uni-freiburg.de>, www-ws-arch@w3.org

I would personally appreciate it if you would explain this a little more
fully.

-----Original Message-----
From: Sai Surya Kiran Evani [mailto:evani@informatik.uni-freiburg.de] 
Sent: Saturday, August 09, 2003 10:44 AM
To: www-ws-arch@w3.org
Subject: Re: Issue: Synch/Asynch Web services



Hi,

Just curious if there would be anything defined regarding the queueing 
behaviour of a web service. I guess the analysis of the systems involved

- the provider or the invoker would be different in the cases of 
unbounded queues and bounded queues..

Thanks,
Kiran.


Geoff Arnold wrote:

>
>> Bottom line: From my point of view async/sync is a question of 
>> blocking or not, and completely separated from the underlying 
>> protocol. It just has to provide sufficient ways to handle the 
>> message exchange in the way desired by the application.
>>
>
> If it were the case that sync/async were merely a question of blocking

> or non-blocking, WSA (and SOAP, and.....) would have nothing to say on

> the subject, since our specifications are silent on the question of 
> implementation.
>
> However there is an alternative viewpoint (that sync/async is a 
> property of message exchange patterns), and this has nothing 
> whatsoever to do with implementation, blocking, threading and so 
> forth.
>
> Geoff
Received on Saturday, 9 August 2003 15:13:20 GMT

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