Issue 130: Asynch request/response HTTP binding needed

[Reviving this thread for the telcon this week.]

Sanjiva's mail below lays out the proposal on the table, and the primary
issue with it - that it requires the use of an addressing mechanism,
presumably an extension engaged in the WSDL and marked required.  Have
we learned anything new since January?

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
On
> Behalf Of Sanjiva Weerawarana
> 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 Tuesday, 22 June 2004 11:10:19 UTC