3 ms·
IIRC chrome is now racing QUIC and HTTP(2) connections instead of doing negotiation/upgrade to detect QUIC support. So this argument (if true) has fallen apart
by SahAssar 6y ago
IIRC chrome is now racing QUIC and HTTP(2) connections instead of doing negotiation/upgrade to detect QUIC support. So this argument (if true) has fallen apart just a few years later.
- tptacek 6y agoIsn't that because QUIC doesn't overload 443/tcp, and sending a UDP packet is extremely cheap? It's not the packets that kill you, it's the round trip latency.
- SahAssar 6y agoMy point was that they could just as well race the DNS lookups, right?
- yencabulator 6y agoThat doesn't solve all the problems listed in https://news.ycombinator.com/item?id=23648497 https://news.ycombinator.com/item?id=23648497 and likely makes the buggy DNS resolver issue worse.