- From: Kagami Sascha Rosylight <notifications@github.com>
- Date: Wed, 23 Apr 2025 08:55:32 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 23 April 2025 15:55:36 UTC
saschanaz left a comment (w3c/push-api#400) Firing the event when revoking makes sense because we want app servers to know that the endpoint is invalidated. This PR is a bit further than that as this is paired to [the blink prototype](https://groups.google.com/a/chromium.org/g/blink-dev/c/BYoV9Zrn6Os/m/0l4NTg2jAgAJ) that wants to do auto resubscription from regrant, which we do not implement. Maybe this PR should be more about resubscription than regrant. In section 3.3.1: > A [user agent](https://w3c.github.io/push-api/#dfn-user-agent) or [push service](https://w3c.github.io/push-api/#dfn-push-service) MAY choose to refresh a [push subscription](https://w3c.github.io/push-api/#dfn-push-subscription) at any time, for example because it has reached a certain age. We can say a user agent may choose to revive a subscription at any time, and then we can stop discussing about regrant because resubscription on regrant will be an implementation detail. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/pull/400#issuecomment-2824780809 You are receiving this because you are subscribed to this thread. Message ID: <w3c/push-api/pull/400/c2824780809@github.com>
Received on Wednesday, 23 April 2025 15:55:36 UTC