Re: [w3c/ServiceWorker] Should EventSource and WebSocket be exposed in service workers? (#947)

Thank you @zdila. Then, I recommend that you switch to use that method (two pushes) for this use case. As Anne said and flaki summarized at https://github.com/w3c/ServiceWorker/issues/947#issuecomment-255223776, that WebSocket may get closed when the Service Worker instance is shut down even if the server didn't intend to signal ring_end.

> to reuse existing API which is now used in several other cases

I see.

----

So, if one has an existing WebSocket based service, it would be convenient if it also works in a service worker though it requires event.waitUntil() to work correctly and shouldn't last for long time. How about background sync + WebSocket in SW?

-- 
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/947#issuecomment-265741207