Update content-addressable-bundles.md #639
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
hayatoito
commented
Mar 17, 2021
hayatoito
commented
- Add a link to issue Content Addressable Bundles #638
- Add "URL integrity" to Goal
- Add "Resource Batch Preloading" to references
|
I've added a link to issue #638 so that a reader can know the position of this proposal, and find easily where they can give feedback. |
- Add a link to issue WICG#638 - Add "URL integrity" to Goal - Add "Resource Batch Preloading" to references
hayatoito
force-pushed
the
content-addressable-bundles
branch
from
05cbcba to
d394f35
Compare
- Update Goal section (Content-Addressability) - Update Cache stragegy section, mentioning a browsers' HTTPCache per Origin. - Add placeholders to Key scenario section as TODOs
- Updare references
|
There are several commits in this PR. I'll do "squash and merge" so that this can be one commit. |
horo-t
reviewed
Mar 18, 2021
| where the bodies of `bundle-C`, `bundle-D`, `bundle-E` are omitted to save the | ||
| cache disk space, the browser can start to fetch them again, possibly in | ||
| parallel. Note that a browser can start to fetch `bundle-D` and `bundle-E` | ||
| immediately without waiting fetching `bundle-C` (and scanning its index |
There was a problem hiding this comment.
My understanding is:
- Web developers should write multiple webbundle link elements in the HTML to fetch the webbundles in parallel if the loading performance is important.
- This nested webbundle format should be used when lazy-loading is important, and the loading performance is not important.
Is my understanding correct?
If so, I don't understand the motivation of browser developers of introducing a new cache mechanism to keep the dependency information. Could you please explain this?
There was a problem hiding this comment.
A good question!
It's fine for a browser to prefetch nested bundles even if a user doesn't request it explicitly.
- If a user requests prefetch via
<link>elements explicitly, browser should prefetch it. - If a user doesn't request it via
<link>elements, a browser doesn't have to prefetch it, but may prefetch it, enabling the content to load instantly if and when the user requests it.
- Add FAQ: WebBundles for Ad Serving use cases - Add FAQ: Subresource Integrity
- Add FAQ: More flexible way for mapping.
- Mention Merkle Integrity Content Encoding - Some editorial fixes
|
Let me close this PR since I don't have a plan to work on this soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.