Re: [w3c/push-api] Retry push event (#300)

Two other considerations:

1. [Section 11.2.2](https://www.w3.org/TR/push-api/#receiving-a-push-message) point 7 of the spec seems to mention a sort of retry mechanism:
> If all the promises resolve successfully, acknowledge the receipt of the push message according to [RFC8030] and abort these steps.
> If the same push message has been delivered to a service worker registration multiple times unsuccessfully [...]
> [...] allowing at least three attempts is recommended

Does it mean that if the fetch `Promise` fails, then the `push` signal is retried again? That would be exactly what I am asking.

2. @martinthomson You say that the application server should make retries when a message is not delivered. Suppose that every 30 minutes, for each endpoint, the application server checks if it has pending deliveries and in that case it sends a new push signal to that endpoint. Apart from the **huge amount of useless requests that the *push service* would get**, I think that each signal would create a separate `push` event: the first successful event processed will display all the pending notifications fetched from server, while **all the other additional events will not display notifications... that would create problems with `userVisibleOnly`**.

-- 
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/push-api/issues/300#issuecomment-418109808