3 ms·
No, it doesn't. Why do you think they made HTTP/3? Because the whole idea of multiplexing multiple parallel streams onto a single sequential TCP stream is stupi
by mgaunard 4y ago
No, it doesn't. Why do you think they made HTTP/3? Because the whole idea of multiplexing multiple parallel streams onto a single sequential TCP stream is stupid.
As it says in the thing you quoted, the correct approach is to use multiple TCP connections.
The only advantage of HTTP/3 over that is that it only pays for the latency overhead of connection establishment once instead of once per stream. This is a very small optimization that is only relevant in a very narrow set of cases.
- preseinger 4y agowhat on earth are you talking about? making 10 concurrent HTTP GET requests to the same server should not require you to make 10 connections to that server muxing multiple logical connections/streams over a single physical connection is, like, networking 101 type stuff you're out of your element donny, go home