Initial reprioritization of use cases #3
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
Make subresource bundling the main use case. Move the remaining use cases to an appendix.
Add "binary" and "request headers" as requirements of the Subresource Bundling use case. Packages in version control is a non-controversial use case.
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.
As discussed in the WPACK group, I have been working to move the controversial use cases to an informative appendix.
This first PR only moves some sections without changing their contents. Later on, we can have more specific PRs to rewrite some of those sections.
One of the main concerns about the Web Bundles proposal has been whether it could allow an origin to act on behalf of another without a client ever contacting the authoritative server. Therefore. my (very rough) initial approach has been to move to the Appendix those uses cases that required signing and/or that called for putting content from different origins inside a bundle.
This affected some use cases that are useful and not really controversial by themselves (e.g. saving a local copy of a website); in following PRs we can update their contents and move them to the main Use Cases section.