Split the Subresource Loading with Web Bundles Explainer into two parts 1) core part and 2) extension parts. #641

hayatoito · 2021-03-24T08:45:52Z

It would be better to split the Subresource Loading with WebBundles Explainer into two parts 1) core part and 2) extension parts.

Core part, which explain the common basic APIs for Subresource Loading
Extension parts:
- Support urn::uuid resources and opaque origins (for use case WebBundles for Ad Serving #624)
- Any other extensions...

We might want to split an explainer into two files, physically, so that separation (and API boundary) would become clear.

By having a core part, we hope we can find a common part in various proposals, and we can write extension parts on the top of it and discuss separately.

Related issue: #623

jyasskin · 2021-03-24T17:55:37Z

Do we think subsetting belongs in the core, or as https://lowentropy.net/posts/bundles/ suggests, should we treat it as one of the first extensions?

hayatoito · 2021-03-25T02:42:38Z

A good question. That's what we have to explore and decide, however, my current rough thinking (based on my early impression) is:

Core:

Explainer: Subresource Loading with Web Bundles (Define a basic loading semantics from a bundle)

Extensions:

Dynamic Web Bundles (subsetting; resource batch preloading). (We need a server side support as an extension)
Support urn:uuid resources and opaque origins (for use case WebBundles for Ad Serving #624)
[Just proposal] Declare dependencies to external bundles (should be separated from Content Addressable Bundles proposal)
[Just proposal] Content Addressable Bundles
Any others...

Just my idea as a starting point of a discussion.

…tension part (WICG#623 WICG#641) This is the almost mechanical *refactoring*, splitting the subresource-loading explainer into the core part and the extension part. The related issues are WICG#624 and WICG#641. In a follow-up PR, we might want to refine the core part so that we can write extension parts more easily, such as having well-defined terminologies and hook points.

#645) * Split the subresource-loading explainer into the core part and the extension part (#623 #641) This is the almost mechanical *refactoring*, splitting the subresource-loading explainer into the core part and the extension part. The related issues are #624 and #641. In a follow-up PR, we might want to refine the core part so that we can write extension parts more easily, such as having well-defined terminologies and hook points.

hayatoito mentioned this issue Apr 2, 2021

Split the subresource-loading explainer into the core part and the ex… #645

Merged

hayatoito added the subresource-loading label Apr 6, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Split the Subresource Loading with Web Bundles Explainer into two parts 1) core part and 2) extension parts. #641

Split the Subresource Loading with Web Bundles Explainer into two parts 1) core part and 2) extension parts. #641

hayatoito commented Mar 24, 2021 •

edited

Loading

jyasskin commented Mar 24, 2021

hayatoito commented Mar 25, 2021

Split the Subresource Loading with Web Bundles Explainer into two parts 1) core part and 2) extension parts. #641

Split the Subresource Loading with Web Bundles Explainer into two parts 1) core part and 2) extension parts. #641

Comments

hayatoito commented Mar 24, 2021 • edited Loading

jyasskin commented Mar 24, 2021

hayatoito commented Mar 25, 2021

Core:

Extensions:

hayatoito commented Mar 24, 2021 •

edited

Loading