Re: [w3c/ServiceWorker] Allow active worker to immediately evict itself (#1296) from Asa Kusuma on 2019-09-15 (public-webapps-github@w3.org from September 2019)

From: Asa Kusuma <notifications@github.com>
Date: Sun, 15 Sep 2019 01:01:43 -0700
To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/ServiceWorker/issues/1296/531544123@github.com>

https://github.com/w3c/ServiceWorker/issues/1016 solves part of the problem. The rest of the problem is around edge cases that we have observed empirically. I.e the server is serving a new version, update is called, but we observe that the old worker is still doing things. The update flow works 99.9% of the time. It would be nice if CSD could handle the other .1%, but it’s difficult for the server to detect that a browser is in this .1%. I have some ideas around how to potentially solve this.

-- 
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/1296#issuecomment-531544123

Received on Sunday, 15 September 2019 08:02:05 UTC