Re: [w3c/ServiceWorker] consider allowing a non-scope identifier for registrations (#1512)

> Taking stateful things that used to have an immutable relation with a registration and now allowing them to move seems to add a lot of complexity. In particular, you would have to move the job queue while you are in the middle of a job running from that queue. This does not seem like a good design option to me.

Sorry, I was not clear.
What I was trying to describe is whether we could remove entirely the scope to job queue map.
Instead you would get the job queue by first getting the registration. The registration to job queue relationship would remain immutable.

> > Allow the scope to registration map to have multiple keys pointing to the same registration
> 
> I'm not sure how this helps to be honest. I guess you are saying allow "old scope" and "new scope"

It was not really old scope vs. new scope but more a way of implementing your idea of a registration with a list of scopes.

> Anyway, if there is time I'd like to discuss this proposal at one of the TPAC meetings this being discussed in #1536.

Sounds good to me.

-- 
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/1512#issuecomment-712253969