Use Socket.io in lib/server.js instead of websockets and xhr about peerjs-server

[shichongrui]

I'm not sure that this would be beneficial considering that the browsers that are going to support WebRTC aren't going to have issues with web sockets.

[celevra]

also after working a few day's with your server it seems like it is very unstable in conjunction with nginx as proxy and express, setting trust proxy and so on doesn't helped, got a lot of disconnects, no auto reconnect and so on... My socket.io is very stable (on the same server, same express, same nginx), so i now try to run it as separate server (standalone) but i want to run it on port 443 on a separate address ... no chance... so please provide the server part socket.io compatible, don't try reinventing the wheel

[michelle]

What's the benefit of using SocketIO?

[reuben453]

One benefit would be that SocketIO takes care of falling back to long polling, etc in case websockets are not supported by the client. Another is that the code becomes a little simpler.
However, the client side peerjs library doubles in size to about 100KB. I'm not sure if the advantages outweigh the disadvantages....

[reuben453]

That should also mean that xhr is not required...

[celevra]

+1
for me it would better fit into an application with allready existing socket.io server, i need authentification and separation, i have to code all that again because i have to use the peer.js server

[dlinx]

+1

[pculka]

+1

[afrokick]

We'll remove xhr long pooling in next major version.

As said @shichongrui modern browser with WebRTC should support WebRTC.