Re: [w3c/ServiceWorker] Find a way for service workers to get their current state (#1077)

it is past a lot of time ago when i wrote about this problem .... if i remember correctly in my case i was searching a listener inside the service for all the states of service worker. My idea it was a bit advanced , a bit more for actual html5 :). Service worker is designed with many problems : 
-impossible to trace when browser startup/closing. Service worker life cicle might simulate to start when the browser is starting and closing as a real service (a kind of daemon in linux) even if it is running really just when a event is executed ;
- impossible to wake up connections (web socket for example) or being triggered by on message event (the main scope of a service in computer science is to execute background code without user interation and to intercept async events from external universe. No ones of them is present in service worker)
- service worker might simulate completely a service : a kind of process working independently by user interation ... instead it is pratically bind to the user interation.  
Service worker might be redesigned exteding all the missing parts 

-- 
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/1077#issuecomment-291616082