- From: Jake Archibald <notifications@github.com>
- Date: Tue, 06 Jun 2017 04:02:18 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 6 June 2017 11:03:12 UTC
@laukstein > why not The addition of new features needs to be justified. It's more "why" than "why not" (see [burden of proof](https://en.wikipedia.org/wiki/Philosophical_burden_of_proof)). I haven't considered security issues with your proposal, but there's no point in adding it if we already have a feature that achieves roughly the same thing, and more. > Imagine array with `urlsToCache` is generated with JavaScript before navigator.serviceWorker.register ... > today there are no way to get it work without impact on performance, like storing in IndexedDB Are you sure this is bad for performance? If you're using this as part of an installing worker it isn't blocking anything, and any performance penalty is surely minuscule compared to the network activity. > or place in sw.js?query-url-with-all-urlsToCache... Can you explain why this would perform worse than your proposal? -- 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/1157#issuecomment-306452894
Received on Tuesday, 6 June 2017 11:03:12 UTC