- From: Yoshisato Yanagisawa <notifications@github.com>
- Date: Thu, 31 Jul 2025 22:47:52 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 1 August 2025 05:47:57 UTC
yoshisatoyanagisawa left a comment (w3c/ServiceWorker#1784) I follow @mkruisselbrink's idea. To implement this, what if we add a new algorithm to the Storage spec like "To obtain a local storage bottle map given a storage key"? It could live in section 4.6 "Storage bottles". The ServiceWorker specification could then call this new algorithm with the registration's storage key and the identifier "caches". This would cleanly replace the current "name to cache map" concept. Does this sound like a good approach? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1784#issuecomment-3142381813 You are receiving this because you are subscribed to this thread. Message ID: <w3c/ServiceWorker/issues/1784/3142381813@github.com>
Received on Friday, 1 August 2025 05:47:57 UTC