Oliver Fromme wrote:
It's probably not useful for HTTP, because most of these should be "keep alive" and/or use transfer encodings (which Apache does by default for HTTP/1.1 connections).
Most large sites don't use keep alive. It ties up a worker thread waiting for another request to come from your home PC, whose link is this slow megabit-plus high-latency straw compared to our OC-48 firehose which is 3-4 hops from MAE East.
The big wins might be in content delivery (video downloads). In this case, you *have* to keep the connection open or risk a poor user experience. However, you can't use this if per-user DRM must be applied to the stream.
