- From: Martin Thomson <notifications@github.com>
- Date: Sun, 02 Sep 2018 17:46:38 -0700
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 3 September 2018 00:47:00 UTC
There are two network errors you are talking about here: 1. The *push service* is inaccessible. In that case, you don't get a `push` event. The browser keeps trying to get to the push service. This is entirely normal; we expect the browser to be occasionally offline, it's a core use case even. 2. The *application server* is inaccessible. In that case, the `push` event is delivered, but the service worker has trouble executing. That's up to the service worker to manage. It might use the application server to assist it in that (the application server might send another push message if it doesn't get contacted in a reasonable amount of time), but that's on your application - the push API has done its part of the work. -- 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-417972702
Received on Monday, 3 September 2018 00:47:00 UTC