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

Your example parameters seem like data that should be inlined into the body of your sw.js script or its dependencies (once https://github.com/w3c/ServiceWorker/issues/839 is implemented in all browsers so that changes to dependencies can trigger updates).  This avoids introducing a de facto new storage API and provides clear semantics around ServiceWorker updates.  (It's also a win/win from a browser engine and SW author perspective because there's no extra moving parts that could delay SW startup.)

Note that your script URL can be something like `sw.js?foo=bar&baz=foo` with your server inlining the parameters into your script.

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