- From: Ben Kelly <notifications@github.com>
- Date: Wed, 14 Oct 2015 09:24:50 -0700
- To: slightlyoff/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Wednesday, 14 October 2015 16:25:17 UTC
> Edit: Not quite true. Cache.put will complete without a SW. Cache.add is essentially a fetch + cache.put so if the SW dies before the fetch completes then cache.put won't be called. For posterity, gecko also treats Cache.add() as a service-worker-side fetch+put. We hold the service worker alive until it completes, however. This is largely due to implementation details, but also makes the developer experience more consistent. I just wanted to note this as it may create different and unexpected behavior for people trying to figure out different service worker caching strategies. --- Reply to this email directly or view it on GitHub: https://github.com/slightlyoff/ServiceWorker/issues/574#issuecomment-148105937
Received on Wednesday, 14 October 2015 16:25:17 UTC