4 ms·
> HTTP/2 was designed to address this problem using multiple "streams" built into a single connection. Multiple objects can be sent over a stream in parallel by
by moviuro 9y ago
> HTTP/2 was designed to address this problem using multiple "streams" built into a single connection. Multiple objects can be sent over a stream in parallel by multiplexing them into the connection. That helps, but it creates a new problem: the loss of a single packet will stall transmission of all of the streams at once, creating new latency issues. This variant on the head-of-line-blocking problem is built into TCP itself and cannot be fixed with more tweaks at the HTTP level.
[0] https://lwn.net/Articles/745590/ https://lwn.net/Articles/745590/
- fsiefken 9y agothanks for the succinct explanation, I also found these two bits: https://ac.els-cdn.com/S1877050915016853/1-s2.0-S1877050915016853-main.pdf https://ac.els-cdn.com/S1877050915016853/1-s2.0-S18770509150... https://www.callstats.io/2017/02/03/web-protocols-http2-quic/ https://www.callstats.io/2017/02/03/web-protocols-http2-quic...