Re: [w3c/ServiceWorker] Include imported scripts to byte-check (#1023)

> When the imported scripts are checked, we're doing it with no-cache, but then later when we run the script it'll execute importScripts and once again request the resources no-cache.

How about:

1. The byte-for-byte check could populate a "script resource map" like `importScripts()` does now.
2. Then the that "script resource map" can be set as the SW's map.
3. The `importScripts()` algorithm could then check the map before going to network/http cache.
4. After script eval or install would need something to remove resources put in the map in step (1), but no longer used by the new service worker script.  This is annoying, but not too with some book keeping.

Note, step (3) would also fix any issues where we go to network/http cache multiple times if script eval calls `importScripts()` multiple times.

-- 
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/pull/1023#issuecomment-267043753