[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

Reorient repository around "bundle preloading" #21

Open
littledan opened this issue Mar 18, 2021 · 1 comment
Open

Reorient repository around "bundle preloading" #21

littledan opened this issue Mar 18, 2021 · 1 comment

Comments

@littledan
Copy link
Collaborator
littledan commented Mar 18, 2021 •
edited
Loading

Following the discussion in IETF 110's WPACK WG meeting, there is a call for adoption of the "bundled responses" file format. This repository should be rearranged to focus on subresource loading, deferring the file format to the new WPACK repository once it is created.

I think it would be best if subresource loading initially focused on a simpler, imperative mechanism along the lines of this gist (which Shubhie from the Chrome team pointed out to me would be more accurately thought of as "prefetching" than preloading). Such a mechanism would form a flexible basis for the output of tools in the near-term, and a higher-level manifest-based mechanism as is currently described for subresource loading could be built on top of it.

With these changes, this repository might be more accurately called "WICG/batch-prefetchingbundle-preloading".
@littledan littledan mentioned this issue Apr 14, 2021
Open
19 tasks
@kinu
Copy link
kinu commented Apr 15, 2021

(Naming bikeshed warning) Hi Dan, it's not super clear why "prefetching" is more accurate than preloading here to me, at least in a resource-hints terminology 'preload' means loading resources in advance for the same page, while 'prefetch' means loading resources for the next navigations. While if you're focusing more on the part that 'prefetch' usually loads resources into HTTP cache (while 'preload' may do a bit more) yes maybe, but with the reason I mentioned earlier (i.e. for the current page vs next pages) I doubt that renaming 'prefetch' is strictly better than 'preload'.

@littledan littledan changed the title Reorient repository around "batch prefetching" Reorient repository around "bundle preloading" May 14, 2021
@felipeerias felipeerias mentioned this issue Jul 30, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@littledan @kinu