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

Re: Asynch request/response HTTP binding needed

From: Mark Baker <distobj@acm.org>
Date: Sat, 31 Jan 2004 14:49:10 -0500
To: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Cc: Martin Gudgin <mgudgin@microsoft.com>, Philippe Le Hegaret <plh@w3.org>, David Orchard <dorchard@bea.com>, Web Services Description <www-ws-desc@w3.org>
Message-ID: <20040131144910.Q3343@www.markbaker.ca>

On Sat, Jan 31, 2004 at 06:45:56AM +0600, Sanjiva Weerawarana wrote:
> 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

Shouldn't #3 be a SOAP request?  That would be more HTTP friendly.
You'd either need an HTTP extension equivalent to SMTP TURN/ETRN to
"turn the connection around", or create a tunnel via CONNECT, in order
to make this a visible interaction to HTTP intermediaries.

Mark.
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Received on Saturday, 31 January 2004 14:50:13 GMT

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