Re: [w3c/ServiceWorker] What does "the registration’s storage key’s name to cache map" mean? (Issue #1784)

annevk left a comment (w3c/ServiceWorker#1784)

From the Storage Standard perspective ideally no specification has to know the details of a storage key or rely on it. Through an environment they get their scoped data structure and then operate on that.

So from a storage bottle you'd get the relevant registration and cache.

Currently the service worker specification attempts to handle its own storage logic and scoping across a user agent, but that shouldn't be needed if we can adopt the storage bottle concept.

Now I don't know for sure it all adds up and we might have to add some things to make it work, but anchoring all the storage aspects in the Storage Standard should be the way to go. That way it's also cleared that when storage is cleared it applies to Service Workers, quota will account for Service Workers, etc.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1784#issuecomment-3154140113
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1784/3154140113@github.com>