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

WebSockets provide a reasonably low-latency persistent channel for things like games. I was looking into whether and how Service Workers could be utilized to allow a user to load (offline and/or quickly) an in-progress game from the last-known state, while still allowing low-latency updates when the network is available. It sounds like Service Workers may not be suitable for this use, if they are expected to be short-lived. It does however seem desirable to allow low-latency asynchronous messaging when it's available, and otherwise fall back to last-known state. This seems relevant to the conversation here, then; I'm wondering if there is some combination of proposals that could replace WebSocket's persistence and latency in this context? I'm not sure I am grokking such an option from the comments here...

-- 
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-315647524