Re: [w3c/ServiceWorker] Proposal: pass custom params in ServiceWorkerRegistration for future use (#1157)

@laukstein Can you elaborate on your use-case, particularly in how it would work in terms of updates?  It's not clear to me whether you want to use the parameters to avoid having to include, for example, https://github.com/GoogleChrome/sw-toolbox configuration in the SW script itself.  Or if the parameter would be something higher level, such as picking which branch/release of an app to use (such as is discussed in https://github.com/w3c/ServiceWorker/issues/1085).

Also of relevance is how you would plan to detect and correct ServiceWorkers stuck with a bad parameter configuration.

Aside: If you're concerned about additional downloads of sw.js, you may also want to consider using useCache=true and ensuring your server has appropriate cache settings, because SW's really like to do update checks.  If things aren't well-cached then the script and all its dependencies could be re-downloaded so that the byte-wise comparison check can be performed.

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