- From: <paul.downey@bt.com>
- Date: Thu, 8 Jul 2004 13:48:40 +0100
- To: <umit.yalcinalp@oracle.com>, <jmarsh@microsoft.com>
- Cc: <www-ws-desc@w3.org>
Ümit wrote: >> Jonathan Marsh wrote: >> Also, how does this address Paul's concern at >> http://lists.w3.org/Archives/Public/www-ws-desc/2004Jul/0043.html? > > I believe Paul's concern is addressed by requiring the mandatory > extension to be declared in WSDL. The addressing mechanism engaged > will provide the operation name to be present in the message exchange > regardless whether it is async binding or not. > > Paul? my concern about asynchronous routing was muddled in that for a moment i saw dispatching a message received asynchronously differently to those framed in a synchronous conversation. i've now come to my senses and realise they are identical and whatever proposal is used to resolve issue 168 should also resolve this 'issue'. i'm not, yet, convinced that WSDL (the language) should require a mandatory dispatching mechanism, however limiting the scope of 'mandatory' to within the RPCstyle does makes sense to me. Paul
Received on Thursday, 8 July 2004 09:04:11 UTC