Re: [quicwg/base-drafts] HTTP/3 priorities are too complex for a majority of implementations (#2739)

[Patrick Meenan <[e-mail]>]

The other big change discussed yesterday by moving away from a tree we can move from a relative priority structure where each request needs to know about the others on the same connection to an absolute priority scheme where priority can be tied to the request itself without extra knowledge. Within the HTTP/2 implementation itself it may not make a big difference but exposing it as an API on the client and server side becomes much easier (and it allows for merging of priority decisions made on the client and server sides). 

A simpler API could always be mapped to the tree but managing equivalent mappings on both ends can become unwieldy if you have multiple clients you don't control or talk to servers you don't control.

-- 
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/issues/2739#issuecomment-494803775