multiplexing

Thanks to Google and Stack Overflow, I think I understood the difference between regular HTTP pipelining and HTTP multiplexing (e.g., with SPDY), so I made the diagram below to show the differences between pipelining and multiplexing based on three regular HTTP requests. My two questions are: Is the image correct? Is it true that if pipelining would not have the head-of-line blocking problem it would be as fast as HTTP multiplexing? Or did I miss an additional difference? igrigorik It's not incorrect, but there is an important aspect it omits. HTTP requires that you deliver the entire response

Is it because it requires the responses to be made to client in the order of request that causes the head of line blocking problem in HTTP 1.1? If each request takes exactly an equal amount of time, then there won't be head of line blocking and HTTP 1.1 pipelining and would perform same as that of HTTP/2 multiplexing? (let's say there is no request priority in HTTP/2 requests and disregard other changes of HTTP/2 such as header compression, binary, etc.) HTTP/1.1 pipelining still requires the requests to be returned in full, in the order requested. HTTP/2 allows the requests responses to be