2 ms·
The author doesn't understand HTTP pipelining, and is drawing completely incorrect conclusions as a result. First, the fact that HTTP requests are pipelined in
by cperciva 18y ago
The author doesn't understand HTTP pipelining, and is drawing completely incorrect conclusions as a result.
First, the fact that HTTP requests are pipelined in the network doesn't mean that HTTP requests have to be pipelined in the server. HTTP server support for pipelining can be as simple as "be aware that there may be more requests sitting in the receive buffer after the one we're currently reading", and in most situations (where the time it takes to service a request is far less than internet RTT) this alone provides a huge speedup.
In fact, I'm not aware of any HTTP servers actually processing pipelined requests in parallel.
HTTP Pipelining is not intended to do anything to mitigate server request-handling latency. It's all about cutting out network RTTs, and if you have to download hundreds of small files (e.g., small images on a web page) it does this very well.