- From: Matt Falkenhagen <notifications@github.com>
- Date: Wed, 10 Oct 2018 21:20:21 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 11 October 2018 04:20:42 UTC
Yea that was phrased unclearly. The lame duck worker is allowed 5 minutes of being the active worker then it gets kicked out. Letting the old worker stay alive to finish inflight requests, but activating immediately and sending new events to the newly active worker also seems like a possible approach. -- 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/1295#issuecomment-428815626
Received on Thursday, 11 October 2018 04:20:42 UTC