4 ms·
The networking overhead of serial requests would be reduced by multiplexing in Http2, i.e., multiple http requests/responses can reuse the same tcp connection i
by la_fayette 5y ago
The networking overhead of serial requests would be reduced by multiplexing in Http2, i.e., multiple http requests/responses can reuse the same tcp connection in parallel...
- bawolff 5y agoI dont think that helps much in this case (or not any more than http/1.1 keep-alive did).
- la_fayette 5y agoMultiplexing is completely different from keep-alive. With http2 a web browser requires one tcp connection per website as communication is in parallel, approaches like conncatenating several css files into one have no use with http2 anymore! Http1 keep-alive allows reusing the same tcp connection for sequential requests/responses only.
- bawolff 5y agoOh i know, i just don't think it helps in this situation, as waiting on the tcp connection is not the hold up in this situation.