Re: [w3c/ServiceWorker] consider fetching service worker scripts with no-cache by default (#893)

I've heard some concerns about effect on QPS for big sites. There are three proposed changes that will affect QPS:

1. whether imported scripts are included in the byte-to-byte comparison (#839)
2. whether to skip the HTTP cache by default for the main script (#893)
3. whether to skip the HTTP cache by default for imported scripts (#893)

I'm not sure we've discussed the impact on making import scripts both involved in the byte-to-byte check (1.) and making it no-cache by default (3.) particularly when importScripts is for a cross-origin resource. Jake seems to have raised the concern in the Aug 4 comment https://github.com/w3c/ServiceWorker/issues/893#issuecomment-237287202 but there are no replies here about it, although the F2F did get consensus to go ahead with (3.).

I guess it's unclear whether the impact of both (1.) and (3.) have been considered together yet. Have they?

-- 
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/893#issuecomment-266638234

Received on Tuesday, 13 December 2016 04:34:03 UTC