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.

Right. I concerned about this too, but it was still better than invoking Run Service Worker for every navigation.

> "Check If Service Worker Resources Are Identical" could return a boolean as it does now, but also a map of all the scripts it fetched.

It seems a bit irony that we should introduce this kind of temporary cache to support bypassing HTTP cache. But yeah I think this is definitely a way to avoid the double-fetch of the seemingly identical resource (unless the content is dynamically changing in the server.) I'd like to also hear opinions from @wanderview and @mattto.

-- 
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-266925189

Received on Wednesday, 14 December 2016 02:30:35 UTC