• Reconnect in WebSocket.onclose() call back
  • Type different Requests and Responses, for example:
    • LoadRequest and LoadResponse

Note: Socket.IO is not a WebSocket implementation. Although Socket.IO indeed uses WebSocket as a transport when possible, it adds some metadata to each packet: the packet type, the namespace and the ack id when a message acknowledgement is needed. That is why a WebSocket client will not be able to successfully connect to a Socket.IO server, and a Socket.IO client will not be able to connect to a WebSocket server (like ws://echo.websocket.org) either. Please see the protocol specification here.
https://www.npmjs.com/package/peer 7,727 dl; depends on ws
Copy link
On this page
Best Practices
Random Maybe Useful Links