- From: István Szmozsánszky <notifications@github.com>
- Date: Thu, 20 Oct 2016 13:48:29 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
Received on Thursday, 20 October 2016 20:48:56 UTC
I was wondering, is there any legit use case for having WebSockets in service workers? Considering the service worker isn't something long-running, and WebSockets are best utilized when the connection built up with the (relatively expensive) handshake lasts longer I couldn't come up with a good usecase. (fwiw being able to host "sub-workers" and run socket connections in there does seem to solve this and sounds like a better usecase for me) -- 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-255223776
Received on Thursday, 20 October 2016 20:48:56 UTC