W3C home > Mailing lists > Public > www-ws-arch@w3.org > July 2002

Re: Asynchronous WebServices

From: Jean-Jacques Moreau <moreau@crf.canon.fr>
Date: Tue, 09 Jul 2002 17:59:27 +0200
Message-ID: <3D2B085F.DA60E206@crf.canon.fr>
To: Naresh Agarwal <nagarwal@in.firstrain.com>
CC: Hugo Haas <hugo@w3.org>, www-ws-arch@w3.org

Hi Naresh,

I think it is reasonnable to expect that the XMLP WG will not produce any
other MEPs for SOAP 1.2. However, the framework for MEPs is quite open, and
so it is partly up to motivated individuals to provide additional MEPs.

Although it is reasonnable to discuss SOAP 1.2 and WSDL 1.2 issues here (and
elsewhere), you may wish to continue discussion intead here [1] for SOAP 1.2
and there [2] for WSDL 1.2. Unlike crossposting, this will help both WGs
track issues better.

With best regards,

Jean-Jacques.

[1] mailto:xml-dist-app@w3.org
[2] mailto:www-ws-desc@w3.org

Naresh Agarwal wrote:

> SOAP1.2 explicitly defines currently only two MEPs, but none of these
> covers *asynchronous messaging*.
>
> Are more MEPs expected in SOAP1.2?
>
> > WSDL 1.2 does have an explicit requirement (R097[3]) to allow
> > description of asynchronous message exchange patterns.
>
> Does WSDL1.2 working draft includes
> *description of asynchronous message exchange patterns*
>
> thanks,
> regards,
> Naresh Agarwal
>
> > -----Original Message-----
> > From: Hugo Haas [mailto:hugo@w3.org]
> > Sent: Tuesday, July 09, 2002 1:33 PM
> > To: Naresh Agarwal
> > Cc: www-ws-arch@w3.org
> > Subject: Re: Asynchronous WebServices
> >
> >
> > * 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 12:00:31 GMT

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