2 ms·
HTTP2. In the HTTP2 world, extra requests don't add any additional latency. The browser multiplexes them over a single connection. I think I'd heard that it
by nostrademons 11y ago
HTTP2. In the HTTP2 world, extra requests don't add any additional latency. The browser multiplexes them over a single connection. I think I'd heard that it even uses a common compression dictionary for all requests, which means that boilerplate code that's duplicated between components will get compressed away.
- lenish 11y ago>In the HTTP2 world, extra requests don't add any additional latency. They don't add any additional TCP connection latency, sure. I think it's a bit unrealistic to claim there won't be any congestion of the multiplexed stream which causes additional latency. >I think I'd heard that it even uses a common compression dictionary for all requests, which means that boilerplate code that's duplicated between components will get compressed away. I may be misremembering, but I thought that was just for request headers?
- alwillis 11y ago>I may be misremembering, but I thought that was just for request headers? That's correct: https://http2.github.io/http2-spec/compression.html https://http2.github.io/http2-spec/compression.html.
- alwillis 11y agoHTTP2 also supports server push—the web server sends resources that the browser is going to need without waiting for them to be requested: http://blog.xebia.com/2015/08/23/http2-server-push/ http://blog.xebia.com/2015/08/23/http2-server-push/