Re: [w3c/ServiceWorker] Should a SW client.id persists across Discards/Reloads of the same page? (#1263)

In my use case - https://github.com/inexorabletash/web-locks/blob/master/README.md#management--debugging - I have no dependency either way on the id being re-used across a navigates/restores, as long as at any point in time (1) it is unique to an environment settings object/agent (i.e.. frame or worker) and (2) it matches the SW's client.id (so a SW could roughly correlate).

> Providing the last discarded client ID seems more palatable.

Sounds better to me as well.

Note if we expose the ID to the page/worker (is that actively discussed anywhere, BTW?) this could be done in user-space via the history API. (I think this discussion is somewhat predicated on the History API's single value being seen as too restrictive. But if a page has access to the ID, it could push just that into the history, and then use it as part of a key into another storage mechanism before/after restore.)

-- 
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/1263#issuecomment-359098966