Re: [w3c/ServiceWorker] Does changing updateViaCache mint a new ServiceWorkerRegistration or update them all? (#1189)

> Do we have other persistent state on the service worker that is mutable without installing a new service worker? I don't think we do right now.

No. Not until updating. My point was adding that info to a service worker instead of a registration wouldn't be more useful.

> Also, I find it weird that register() would change state, but not advertise it did so by creating a new registration. Right now if register() resolves the current registration then we know it short-circuited and nothing changed.

Interesting. It seems you think of a JS registration object a thing that represent *the state* of the underlying registration struct. I think we discussed this a way back and settled on the behavior the JS objects for the same registration struct pass equality check. And the registration object's attribute getters return the latest values set by register/update operations. The current implementations reflect that behavior, right?

-- 
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/1189#issuecomment-329676442