Re: [w3c/ServiceWorker] Safety versus simplicity in specification tests (#1087)

IMO, introducing a keep alive protocol across events seems not a good idea. It's against the original design decision that service workers are event-driven and short-running. User agents may also detect and terminate the execution anyway if they regard it an abnormal operation.

I think  "3) sending results to the page on each event" in https://bugs.chromium.org/p/chromium/issues/detail?id=558244 is desirable. But if tests can't be designed in that way and need to span multiple `ServiceWorkerGlobalScope`s' creation/termination, using a storage would be a good direction I think. Can we think about adding some helper functions to make it easier to use a global storage instead of introducing a keep alive protocol?

-- 
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/1087#issuecomment-286616371