3 ms·
That has absolutely no bearing on TCP. A bunch of images could load on a single TCP connection just fine. Don’t confuse browsers and HTTP with the underlying p
by SanderNL 3y ago
That has absolutely no bearing on TCP. A bunch of images could load on a single TCP connection just fine.
Don’t confuse browsers and HTTP with the underlying protocol.
TCP has its flaws, but I don’t see how HTTP and its request/response monopoly is one of them.
- bastawhiz 3y ago> A bunch of images could load on a single TCP connection just fine. "Just fine" is subjective here. Of course they could load, but with certain performance characteristics. > That has absolutely no bearing on TCP It does, actually. Every packet requires a full round trip done sequentially. H3 significantly relaxes this because it has an understanding of what's actually being transmitted. An unreliable connection will inherently be far slower over TCP than over H3 because any delayed or lost packets or acks need to be retransmitted before the next packet goes out. H3 makes intermittent packet loss affect fewer files being transferred and reduces the impact of latency on a packet-by-packet basis. The vast majority of Internet users aren't on highly reliable broadband. H3 is a win for all of those people.
- SanderNL 3y agoAh! That’s interesting. I have to do some more reading instead of yelling at the clouds. Thanks for that.