Not exactly, no. A persistent connection doesn't imply a lock/step of request/response. As another example, consider a protocol like BitTorrent or Gnutella. You send packets to a host and read packets from a host, but the messages don't happen in sequence. A persistent connection is necessary (because it's long-lived, and knowing you've disconnected is important), but there's no concept of a "request" and "response" -- just arbitrary messages sent & read from the pipeline.
Anyways... this is straying far off topic from HttpComponents. I just wanted remind Oleg that NIO does have it's uses and reasons in many situations. :) Sam On 12/5/07, Ortwin Glück <[EMAIL PROTECTED]> wrote: > > > Sam Berlin wrote: > > I don't think a typical browser is capable of > > handling this, but if you could code your own Socket handling, it is > > useful. > > You mean, to use a connection-less protocol like UDP for instance. > > -- > [web] http://www.odi.ch/ > [blog] http://www.odi.ch/weblog/ > [pgp] key 0x81CF3416 > finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
