[ServiceWorker] Take into accounts etags on initialization importScripts responses to update the Service Worker (#830)

For developers, composition of diverse service worker functionality can be done via `importScripts()`. The problem with this approach is that is needed to byte-alter the sw in order to get it updated. If not, imported scripts could change but the main file could remain the same. Traditional solutions forces the developer to manually add some kind of change in the sw file but the specification could take into account [eTag header](https://en.wikipedia.org/wiki/HTTP_ETag) to determine if imported scripts have changed. If the eTag is not present, it can default to the current behaviour.

This way, even if the sw itself has not changed, a byte-level change in one of the eTag will trigger the update.

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

Received on Tuesday, 9 February 2016 14:46:51 UTC