On Tue, Jul 27, 2010 at 08:01:55PM -0700, Jerry Dunmire wrote: > Thanks for the comments and suggestions. I'm not sure how 'pipelining' > works, but I'll look into it.
A non-pipelining HTTP fetch of a URL looks like this: 1. open TCP connection to server on port 80, 2. transmit HTTP GET request, 3. read reply, 4. close TCP connection. For subsequent fetch from the same server, a new connection is opened. A pipelining HTTP fetch looks like this: 1. open TCP connection to server on port 80, 2. transmit HTTP GET request, 3. read reply, 4. deduce from reply header that pipelining is supported, 5. keep connection open for re-use, 6. transmit another HTTP GET request, etc. Thanks for considering the latency challenged. ;-) -- James Cameron http://quozl.linux.org.au/ _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
