You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually, I've discovered that the internet in general and WebSocket in particular, are not reliable. On my last talk a few days ago I've experienced some issues with low ping and low internet connection speed. Control panel still worked, but it felt uncomfortable.
So, right now I try to find other ways to connect the control panel to the presentation, and audio transport seems very promising to me (see #24) since it will make the server completely unnecessary.
Still, if you want to practice native WebSocket browser API, there is something you can do here.
I think it's not necessary to remove socket.io completely, at least on the server-side. But on the client-side, why not.
Socket.io is used both in the control panel and in the reveal.js plugin, and, I believe, can be replaced entirely with new WebSocket :)
You don't need to use socket.io in 2k17
The text was updated successfully, but these errors were encountered: