Re: [ServiceWorker] Workers & SharedWorkers within ServiceWorkers (#678)

In terms of life-cycle for the Mozilla email case (context: which I also work on), if the ServiceWorker needs to be shut down for memory-pressure reasons (or other reasons), it does seem appropriate to reap the email SharedWorker if there's no active documents keeping the SharedWorker alive.

I don't think that would defeat the point, which as I see it (and @jrburke explained on https://github.com/slightlyoff/ServiceWorker/issues/slightlyoff/BackgroundSync#70 quite well), the main benefit for the email app is the single execution context for the back-end that talks to the mail servers and potentially multiple UI pages.  The ServiceWorker, like a UI page, is a consumer of the back-end but with the very simple goal in the requestsync case of saying "hey, go sync".

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