Re: [w3c/ServiceWorker] _Update algorithm should unregister SW on 404 and 410 errors (#204)

Cache API could be used from main thread for many things. Will browsers browser be able to detect if cache is ServiceWorker only? Unless it will be stored as cache's metadata then probably not.

> Sure, but does this solve the use case of "I tested this on localhost ages ago and I have a bunch of unexpected state on localhost messing up my localhost today"?

Only if the same (hard-coded?) cache name is used, but I see how this may happen too. SW tools should save from this.

> Still, it would be nice to fix the orphaned update case as that uses actually CPU, bandwidth, etc on real sites today.

Can you share stats on how often that happens with how many websites? (assuming Google Plus SW isn't the only case)

-- 
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/204#issuecomment-307566453