Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?

Hi Tom,

> Why is that a misuse of priority? It seems entirely reasonable for a client
> to specify a mostly-linear order. There is a very good reason for this:
> inside HTML pages, CSS links and synchronous scripts must be evaluated in
> the order they appear in the HTML file. This implies that the server should
> send those resources in a linear order. This is exactly the rationale
> behind Chrome using mostly-linear orders. (This is not to say that
> mostly-linear orders are not occasionally problematic -- they are
> <> -- but
> there are good reasons to linear orders at least some of the time.)

Thank you for your explanation.
I did not know this use case.
So, I would like to withdraw my previous word "misuse".


Received on Wednesday, 25 January 2017 04:04:51 UTC