- From: Deep Duggal <notifications@github.com>
- Date: Thu, 13 Apr 2017 14:36:27 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 13 April 2017 21:37:00 UTC
It would be a **wasted opportunity** if one service worker could not register another. The goal of a service worker is to allow scripts to respond to events in the background. Some events will require specific scripts to handle them. Not allowing a service worker to register other service workers will encourage large, service workers that can handle all outcomes and **disfavor smaller, modular service workers** that are built to handle specific tasks. **It would be imprudent, inefficient, and just not cool to do so.** Nonetheless, security is going to be a major concern with this, so it would be best to proceed with caution and perhaps impose some limitations on service workers registering each other. -- 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/1117#issuecomment-294028084
Received on Thursday, 13 April 2017 21:37:00 UTC