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

RE: FYI: synch/asynch def from WSRM TC

From: Cutler, Roger (RogerCutler) <RogerCutler@chevrontexaco.com>
Date: Sat, 24 May 2003 02:14:03 -0500
Message-ID: <7FCB5A9F010AAE419A79A54B44F3718E01817E50@bocnte2k3.boc.chevrontexaco.net>
To: "Geoff Arnold" <Geoff.Arnold@sun.com>, "Ugo Corda" <UCorda@SeeBeyond.com>
cc: www-ws-arch@w3.org
Maybe so, but it looks like a perfectly valid definition and it covers
very common and important usage cases.  Our document currently, without
qualification, recommends that the terms not be used in normative specs.
It appears that this group is perfectly happy to do so and I see no
reason in the world for them not to.
 
-----Original Message-----
From: Geoff Arnold [mailto:Geoff.Arnold@sun.com] 
Sent: Friday, May 23, 2003 8:12 PM
To: Ugo Corda
Cc: www-ws-arch@w3.org
Subject: Re: FYI: synch/asynch def from WSRM TC




On Friday, May 23, 2003, at 09:02 PM, Ugo Corda wrote: 


	I thought somebody might be interested in that group's
definition at [1]. (The definition is limited to the SOAP HTTP binding
case). 

	Ugo 

	[1]
http://lists.oasis-open.org/archives/wsrm/200305/msg00062.html 


Well, yes, as you say: it's limited to HTTP. It doesn't apply to MEPs;
can't address multiparty (obviously) 
or composite interactions..... 
Received on Saturday, 24 May 2003 03:14:53 GMT

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