RE: The deep difference between request/response and fire-and-forget
"David Orchard" <[email protected]>
| Newsgroups | gmane.text.xml.distributed |
|---|---|
| Message-ID | <[email protected]> |
> -----Original Message----- > From: Rich Salz [mailto:[email protected]] > Sent: Monday, January 23, 2006 9:08 PM > To: David Orchard > Cc: [email protected] > Subject: RE: The deep difference between request/response and fire-and- > forget > > > I would say that if closing the connection (wow, I originally typed that > > as if close thing connection..) without waiting for a response is > > invalid HTTP, THEN that means that HTTP can't do Fire and Forget AND > > that an application that would be built on Fire and Forget couldn't be > > deployed on HTTP. > > I'm not so sure. Why can't you do HTTP/FaF by saying that the HTTP server > response is consumed (per the HTTP protocol spec) but ignored? I would think that consuming the response is the opposite of "forget". Consuming the response is effectively not fire and forget. Isn't that the key difference between req/resp and f-a-f? Dave