reprioritize blocking asset files (.js, .css) for Chrome
#349
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment, Chrome falls behind Firefox in prioritizing the asset files, as discussed in http://blog.kazuhooku.com/2015/04/dependency-based-prioritization-makes.html.
This PR implements a workaround in the server-side by raising the priority to maximum of requests that are likely against asset files. The reprioritization is not applied to HTTP2 connections that use priority trees (e.g. Firefox).