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

[Lucas Pardue <[e-mail]>]

Thanks for the clarification. I'm not an expert is the area you describe, so I'll let others step in if they want.

The approach sounds fragile because several factors may work against it. 

Assume a model where a HTTP/2 or HTTP/3 server is best placed to make use of its available bandwidth based on its view of the client wants and the availability of response data. If defering load means that a client holds back requests, then the server knowledge is limited. In this case, if the server experiences delays in accessing image data, it can't serve the lower priority items in the available time window.

Another problem with the approach is connection coalescing. A website may not be aware that the browser is reusing a connection for different domains.

I think prioritisation is important. However, I think the user agent is able to articulate its requirements without a depedency tree. A simpler model of prioritisation may improve the likelihood that the server bothers to use it in decision making. 



-- 
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-494760028