W3C home > Mailing lists > Public > www-ws-desc@w3.org > January 2004

RE: Asynch request/response HTTP binding needed

From: David Orchard <dorchard@bea.com>
Date: Fri, 30 Jan 2004 22:43:56 -0800
To: "'Sanjiva Weerawarana'" <sanjiva@watson.ibm.com>, "'Martin Gudgin'" <mgudgin@microsoft.com>, "'Philippe Le Hegaret'" <plh@w3.org>
Cc: "'Web Services Description'" <www-ws-desc@w3.org>
Message-ID: <00c301c3e7c5$9a278280$6401a8c0@beasys.com>

yup.  I agree.  The issue about the callback address is related but can be
orthogonal to the binding.

Dave

> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
> Sent: Friday, January 30, 2004 4:46 PM
> To: Martin Gudgin; Philippe Le Hegaret; David Orchard
> Cc: Web Services Description
> Subject: Re: Asynch request/response HTTP binding needed
>
>
> "Martin Gudgin" <mgudgin@microsoft.com> writes:
> > PAOS is slightly different. It has two MEPs, the one I think you are
> > thinking of works as follows:
> >
> > Given nodes A and B:
> >
> > 1. node A makes an HTTP GET to node B.
> > 2. Node B sends a SOAP Request as the HTTP response.
> > 3. Node A responds with a SOAP response in an HTTP POST to Node B.
> > 4. Node B responds with some HTTP response ( typically a web page )
> >
> > Gudge
>
> I understood what DaveO wanted as:
>
> 1. node A makes an HTTP POST to node B with a SOAP Request and
>    information on where to POST the HTTP response to
> 2. node B responds with something like 201 OK
> 3. later on, node B makes an HTTP POST to node A with a SOAP Response
> 4. node A responds with something like 201 OK
>
> DaveO??
>
> I like this a lot but unfortunately one needs WS-Addressing
> or something
> similar to send the "information on where to POST the HTTP
> response to".
>
> Sanjiva.
>
>
Received on Saturday, 31 January 2004 01:43:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:28 GMT