Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interfacing with Resource Hints and link rel=preload. #2

Closed
addyosmani opened this issue Nov 16, 2016 · 3 comments
Closed

Interfacing with Resource Hints and link rel=preload. #2

addyosmani opened this issue Nov 16, 2016 · 3 comments

Comments

@addyosmani
Copy link

Something unclear reading through the current proposal is how a developer would hint that some resources in a web package have a higher priority to fetch (e.g via resource hints) than others - the entire package would be fetched with a single priority. If I want to prefetch or preload certain assets, I'm unsure how those systems interface with packages.

Are there any thoughts about this?

@bmeck
Copy link
Collaborator

bmeck commented Dec 2, 2016

@addyosmani I'm not sure that is possible under current text since it is a single non-multiplexed body for the payload. You might want to put the prioritized resources at the start of the package body. I would be interested more in having multiple streams like http/2 does if you want to interleave resources and/or change priorities dynamically.

@bmeck
Copy link
Collaborator

bmeck commented Dec 29, 2016

@addyosmani after a call, it should be possible to re-order signed content resources as long as a Package-Signature and Content-Index can be recomputed by the server. The server could re-order them into a more optimal order. Might be a good idea to move the discussion to #11 since that is going to be covering reordering. Is this ok to close?

@addyosmani
Copy link
Author

Let's close this one up. Thanks for the replies, @bmeck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants