dmitry-korolev / remeal

Reveal.js remote control
MIT License
28 stars 7 forks source link

Remove socket.io dependency #13

Open randomailer opened 6 years ago

randomailer commented 6 years ago

You don't need to use socket.io in 2k17

dmitry-korolev commented 6 years ago

Pull requests are highly welcomed!

mh166 commented 6 years ago

Hi, any hints on how to start about that one?

Where should one begin to dig, where are the dependencies located? Is there anything special to consider when bringing the new solution in place?

Thos would be helpful for getting started. :)

dmitry-korolev commented 6 years ago

Hi, @mh166 Glad to see you here!

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 :)