Re: [w3c/push-api] Expose pushManager on Navigator (PR #368)

Thanks both for weighing in!

1. I think the overloading is nice as it allows for reusing an existing subscription. And that ends up working in both directions. And of course you don't have to implement it as a dummy "service worker registration", that would be more of a specification device.
2. I don't think a window client is a viable key as we wouldn't want two `https://example.com/` windows to end up with separate subscriptions. In fact, `https://example.com/` and `https://example.com/bar` should share a subscription too. (A `ServiceWorkerRegistration` also doesn't seem like it would be persistent enough, but maybe a "service worker registration" is.)
3. I see your point on keying of service worker registrations potentially changing, but that also would have to be opt-in and therefore it doesn't really clash with this scheme and the default would still end up being straightforward and sharing a subscription.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/pull/368#issuecomment-2283779077
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/pull/368/c2283779077@github.com>