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

While thinking about this today I realized that I need to map the global "id to registration" map really have {origin,id} tuples as the key.  Different origins can use the same id values and they should not conflict.

The alternative where we restrict id values to URLs like scope could instead just use the id as the key since the origin would be directly embedded in it.  This would be a bit simpler to implement.

I think I still prefer the ergonomics of the non-URL id, though.  I personally find it confusing when URLs are used as identifiers, but not actually used for anything functional like fetching resources, etc.

Just throwing this out there in case it changes anyone's mind.

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