W3C home > Mailing lists > Public > public-ws-chor@w3.org > June 2003

RE: choreography protocol

From: Ugo Corda <UCorda@SeeBeyond.com>
Date: Sun, 22 Jun 2003 10:28:10 -0700
Message-ID: <EDDE2977F3D216428E903370E3EBDDC9081212@MAIL01.stc.com>
To: "Assaf Arkin" <arkin@intalio.com>, "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
Cc: <public-ws-chor@w3.org>

> >My personal feeling is that its better to just have request-response
> >and not say at the abstract level whether or not the response is on
> >the same channel or not. That's a binding characteristic - the 
> >abstraction is that there's a request and there will be a response.
> >Take an SMTP binding - every response would be on a separate channel
> >vs. and HTTP binding where the response can be on the same channel.
> >  
> >
> I agree.
> I think it should be a matter of protocol selection, and we actually 
> took the liberty in trying to do that with WSDL 1.1 and it 
> seems to work 
> pretty well. With one caveat.
> If you have some process that tends to use other services, as 
> defined by 
> their interface, that insist on such high latency request/response 
> cycles, then obviously you can't invoke that process using 
> HTTP and wait 
> for a response in the same connection. So there needs to be 
> some way to 
> mark the interface as using one means of communication vs another, so 
> you can tell how it affects all other involved parties.
> Perhaps using F&P?
> arkin
> >Sanjiva.

Yes, relying on the WSDL binding works when you can express that binding in your spec. But what if you are writing a spec (e.g. a choreography spec) that prefers to leave WSDL bindings unspecified but still wants to talk about request/response on the same channel vs. on different channels? WSDL right now does not specify any way to express that. 

It looks like BPEL got around this problem by saying that a request/response on the same channel maps to a WSDL request/response MEP, while a request/response on different channels maps to two separate one-way MEPs (where the response one usually gets labeled "callback" as an additional syntactic sugar).

Received on Sunday, 22 June 2003 13:28:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:00:59 UTC