- From: rektide <notifications@github.com>
- Date: Tue, 07 Jan 2020 18:20:24 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 8 January 2020 02:20:26 UTC
I am late in my reply here. I would like to hear some story for how offline-transfered Web Bundles/Web Package are going to work with this feature. If I have a website that uses a cdn such as https://unpkg.com to load modules, and I create a signed Web Bundle for my site, and download a signed Web Bundle of my unpkg.com dependencies, how can I offline share these bundles with a friend & have them get a working web experience? At the moment I don't see how this Partition the HTTP Cache feature can be made compatible with example use case I provided, which fits within the stated intent of the [Use Cases & Requirements for Web Packages](https://wicg.github.io/webpackage/draft-yasskin-wpack-use-cases.html) document. My `example.com` site would need to be loaded while online if the http cache is partitioned, as the unpkg.com signed bundles would reside on a different partition than `example.com`. I hope this partitioning feature can be revised or updated to un-break Web Package/Web Bundle's emerging offline-sharing capabilities a lot of us are eager for. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/424#issuecomment-571861615
Received on Wednesday, 8 January 2020 02:20:26 UTC