Re: Issue 59: A use case -- out-of-phase HTTP

What was your take on the proposal attached to
http://lists.w3.org/Archives/Public/public-ws-addressing/2005Sep/0045.html?

John Kemp wrote:

> Hello David,
>
> ext David Hull wrote:
>
> >One of the use cases captured during the work of the async task force
> >involved a mobile phone or other such mobile device.  In this scenario,
> >the phone would send a dummy HTTP request to an HTTP server.  The HTTP
> >/response/ to that request would contain a SOAP /request /message.  The
> >phone would then process the request and make a second HTTP request to
> >the server.  This /request/ would contain the phone's SOAP /response
> >/message.
>
> >This uses a single protocol (HTTP), with multiple connections, and was
> >put forth as a scenario at least one party (Nokia, as I recall?) would
> >be interested in seeing supported.  Can this scenario be handled by any
> >of the present proposals?
>
>
> I have not yet seen a proposal that fully handles this case. The current
>  PAOS specification [1] uses non-WS-Addressing SOAP header blocks. I
> will note, however, that Dave Orchard did address PAOS in [2], providing
> for the presence of a paos:reverseBinding element in a WSDL document,
> and noting that the paos:reverseBinding would still need to be written.
>
>  If not, do we have a plausible theory about
>
> >how we would handle it?
>
>
> It seems to me that we would merely need to complete the definition of
> the paos:reverseBinding as mentioned in [2].
>
> Cheers,
>
> - JohnK
>
> [1] http://www.projectliberty.org/specs/liberty-paos-v1.1.pdf
> [2]
> http://lists.w3.org/Archives/Public/public-ws-addressing/2005Nov/0014.html

Received on Friday, 4 November 2005 15:45:46 UTC