3 ms·
I'll ask the same question as I did above: Explain to me why any of this is necessary once HTTP/3 is widely adopted? Doesn't it already solve all of these issu
by jiggawatts 6y ago
I'll ask the same question as I did above: Explain to me why any of this is necessary once HTTP/3 is widely adopted?
Doesn't it already solve all of these issues, and head-of-line-blocking as well?
- jkrems 6y agoAFAIK HTTP/3 still only has header compression and does nothing for cross-resource compression. So I'm not sure how it relates to this? I can see ways to model this kind of behavior on top of individual requests but it'd likely be even more complicated than it already is with web bundles. E.g. telling the browser that certain resources shouldn't be fetched because they'll likely be pushed because of a different pending request is super awkward without a "resource bundle" abstraction.
- RonanTheGrey 6y agoHTTP/3 still allows content blocking, and that's what they're trying to eliminate.