Re: [quicwg/base-drafts] HTTP/3 with strict priorities (#2700)

[Dmitri Tikhonov <[e-mail]>]

@kazuho writes:
> While I think this would be a simplification for HTTP/3, it would be an additional complexity for HTTP/2+HTTP/3 as a whole. At the moment, prioritization scheme of HTTP/3 allows implementations to reuse the logic of HTTP/2 prioritization (only what's visible on the wire is different).

This is an important aspect of this discussion.  Extant HTTP/2 stacks can use the current (ID-20) version of HTTP/3 prioritization with few changes.  Radical departures from it will inevitably result in more work for them -- not just in programming effort, but also to research how to use the new prioritization scheme effectively.

To be adopted, a new prioritization model should be substantially and demonstrably better than the current one. The proponents of new schemes should catalogue use cases (as @rmarx also mentions above) for comparison with the current scheme.

Recent reports (both in clients and servers) indicate that HTTP/2 prioritization is already being leveraged to produce substantial performance benefits.  It would be nice if these solutions could be used in HTTP/3 as well.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2700#issuecomment-493491549