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

RE: Asynch Scenarios

From: <paul.downey@bt.com>
Date: Tue, 10 May 2005 19:44:43 +0100
Message-ID: <2B7789AAED12954AAD214AEAC13ACCEF2709E2A9@i2km02-ukbr.domain1.systemhost.net>
To: <michael.eder@nokia.com>, <dorchard@bea.com>
Cc: <public-ws-async-tf@w3.org>

Hi Michael

it would help me (at least) if you could give an example
transport which works this way, so i could understand how
it differes from a one-way underlying protocol


-----Original Message-----
From:	public-ws-async-tf-request@w3.org on behalf of michael.eder@nokia.com
Sent:	Tue 5/10/2005 6:08 PM
To:	dorchard@bea.com
Cc:	public-ws-async-tf@w3.org
Subject:	RE: Asynch Scenarios

Hi David,
I think you're making assumptions about the nature of the two-way underlying protocol, and we should not do that at this time, or at least be a little bit clearer that were making this assumption.  How would your scenarios look differently if instead of assuming the in message went out on the underlying protocols request, it went out on the underlying protocols response?  At the very least, I think we should title the section Two Way Underlying Protocol (with back-channel for returning messages) to distinguish it from a Two Way Underlying Protocol (no channel for returning messages).  From the SOAP perspective I don't think there are any differences than with the one-way, but I'm not so sure about how this could be done with WSDL..
Kind Regards,
Michael Eder
-----Original Message-----
From: public-ws-async-tf-request@w3.org [mailto:public-ws-async-tf-request@w3.org]On Behalf Of ext David Orchard
Sent: May 06, 2005 07:20 PM
To: public-ws-async-tf@w3.org
Subject: Asynch Scenarios

I've posted an update based on Marc H's comments at 



I'll continue to update as soon as I get comments.



Received on Tuesday, 10 May 2005 18:44:51 UTC

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