W3C home > Mailing lists > Public > public-ws-addressing@w3.org > December 2005

RE: Action Item

From: <paul.downey@bt.com>
Date: Tue, 6 Dec 2005 22:06:37 -0000
Message-ID: <2A7793353757DB4392DF4DFBBC9522550276F0C2@I2KM11-UKBR.domain1.systemhost.net>
To: <john.kemp@nokia.com>, <dmh@tibco.com>
Cc: <conor.p.cahill@intel.com>, <umit.yalcinalp@sap.com>, <public-ws-addressing@w3.org>

> Right. There's also the reverse HTTP case, where a SOAP request message
> is sent in the HTTP response, and a SOAP response is then sent in
> response to that SOAP request on a new HTTP channel, causing a response
> to the initial SOAP request to be sent over the new HTTP response
> channel. It's not clear to me that this is exactly polling behaviour. It
> does, however, involve an asynchronous response to the initial message
> (according to the WS-A definition of asynchronous).

John, can you please point to the SOAP HTTP protocol binding that works this 
way, or maybe write it in terms of which HTTP methods are used, and
responses sent back, I'm having real difficulty in understanding this in
terms of RFC 2616.

Received on Tuesday, 6 December 2005 22:06:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:12 UTC