Re: The deep difference between request/response and fire-and-forget from Rich Salz on 2006-01-24 (xml-dist-app@w3.org from January 2006)

From: Rich Salz <rsalz@datapower.com>
Date: Mon, 23 Jan 2006 23:57:38 -0500 (EST)
To: Mark Baker <distobj@acm.org>
cc: David Orchard <dorchard@bea.com>, "xml-dist-app@w3.org" <xml-dist-app@w3.org>
Message-ID: <Pine.LNX.4.44L0.0601232340240.7794-100000@smtp.datapower.com>

> no "breakage" when the connection is closed, because HTTP 1.1 cleanly
> separates message semantics from connection state (HTTP 1.0, not so
> much, though with responses, not requests).  Worst case, closing the
> connection is an inefficient use of resources (the TCP connection),

Sure, if the connection is closed at the "right time."

But if the connection is closed while parts of the response are "in
transit," and the server detects this, it is free to undo the efffects
of the client's operation.

	/r$

-- 
SOA Appliance Group
IBM Application Integration Middleware
* This address is going away; please use rsalz@us.ibm.com *

Received on Tuesday, 24 January 2006 04:57:45 UTC