Re: [ServiceWorker] Define the lifetime of a blob URL created inside a service worker (#688)

I think Gecko's current behaviour is correct. Yes, it may get GC'd when the SW closes, but same with variables. If you want a long term way to store a response, the caches api is the way to go right? 

Tieing it to registration feels wrong as it would need to survive browser shut down.

What is the current behaviour breaking? I'm wondering if a way to access items in the cache api by url may be a better solution. 

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/688#issuecomment-97264203