5 ms·
You are wrong. If you understand how browsers behave when they query a page that contains different resources from one source, and how head-of-line blocking wor
by baby 7y ago
You are wrong. If you understand how browsers behave when they query a page that contains different resources from one source, and how head-of-line blocking works, you understand why so much effort was put into this protocol.
(Any introduction on QUIC will explain you these if you are interest.)
- pdimitar 7y agoSo, as a guy who is hellbent on not losing their ad blocking, are you telling me that QUIC allows the client (the browser in this case) to read from the stream up to a point, find a resource with a well-known name (or crypto hash) that is an ad/tracker, and the client is then allowed to just skip ahead in the stream, not downloading and never parsing the said ad/tracker? If no, then QUIC has failed its purpose, for the tech-savvy browser users at least. If yes, I'd be happy.
- AgentME 7y agoQUIC is just a way for a browser to make more HTTP-like connections in parallel more efficiently. It doesn't affect ad-blocking browser extensions. The browser can still implement the APIs for extensions the same way regardless of whether QUIC or a previous version of HTTP is used.