Re: [w3c/ServiceWorker] A simple globally available store of data per-registration (#1331)

Opening IDB is frequently slow and IDB's API is promise-hostile. Neither
are great arguments, but taken together it creates a real hurdle for
storing global configuration data (e.g., SW "timeout"; a date after which a
SW should stop handling requests and perhaps unregister itself).

On Fri, 29 Jun 2018, 18:20 Marijn Kruisselbrink, <notifications@github.com>
wrote:

> I think Jake's (and at least mine) question is: if this has to be an
> asynchronous API anyway, what's the benefit of having something SW specific
> over just using a "normal" storage API (i.e. cache storage, IDB or some
> not-yet-existing async localstorage style API)?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/ServiceWorker/issues/1331#issuecomment-401419372>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAF8M498WBiXCvTl0bJCFXi8_z4hB4Hsks5uBmHwgaJpZM4U8F_I>
> .
>


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