- From: Hugo Haas <hugo@w3.org>
- Date: Tue, 9 Jul 2002 17:03:20 +0900
- To: Naresh Agarwal <nagarwal@in.firstrain.com>
- Cc: www-ws-arch@w3.org
* Naresh Agarwal <nagarwal@in.firstrain.com> [2002-07-06 16:59+0530] > According to Gartner and other market reseatch agencies, the future of web service lie in *Asynchronous Web Services* > using transport protocols like BEEP, SMTP etc. > > SOAP1.1 and WSDL1.1 donot talk about the asynchrony anywhere. > > Are these standards *complete* in terms of supporting ASYNCHRONOUS web services? > > If not, do SOAP1.2 and WSDL1.2 support asynchronous web services. SOAP 1.2 allows asynchronous modes of operations. As a matter of fact, the requirements document contains tmo use cases of asynchronous messaging: S17[1] and S20[2]. WSDL 1.2 does have an explicit requirement (R097[3]) to allow description of asynchronous message exchange patterns. I would add the asynchrony is shown in several examples in the Web Services Architecture Usage Scenarios[4]. Regards, Hugo 1. http://www.w3.org/TR/2002/WD-xmlp-reqs-20020626#s17 2. http://www.w3.org/TR/2002/WD-xmlp-reqs-20020626#s20 3. http://www.w3.org/TR/2002/WD-ws-desc-reqs-20020429/#desintwserv 4. http://www.w3.org/2002/ws/arch/2/ws-arch-scenarios-20020619.html -- Hugo Haas - W3C mailto:hugo@w3.org - http://www.w3.org/People/Hugo/ - tel:+1-617-452-2092
Received on Tuesday, 9 July 2002 04:03:40 UTC