Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980)

great responses - sorry for rant but having all sorts of issues with service worker at present. please tell me if ive missed something. Push API and firebase messages are working dandy but no geo available in service worker is not good for us as users need to use navigation apps and put our app in background. no geo when app loses focus either. we need a heart beat sent to server from client even if the app loses focus. but service worker stops due to its lifespan limitations.  using firebase pings to wake service worker seems  impractical - or is it?.  are we missing anything fundamental here? can we achieve all of the above with shared workers? without the service worker stopping and when the app loses focus?

-- 
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/980#issuecomment-310411161

Received on Thursday, 22 June 2017 15:16:10 UTC