Ivo Wetzel’s answer doesn’t seem to be valid in Socket.io 0.9 anymore. In short you must now save the socket.id and use io.sockets.socket(savedSocketId).emit(…) to send messages to it. This is how I got this working in clustered Node.js server: First you need to set Redis store as the store so that messages can go cross … Read more
Here is my list (updated for 1.0): // sending to sender-client only socket.emit(‘message’, “this is a test”); // sending to all clients, include sender io.emit(‘message’, “this is a test”); // sending to all clients except sender socket.broadcast.emit(‘message’, “this is a test”); // sending to all clients in ‘game’ room(channel) except sender socket.broadcast.to(‘game’).emit(‘message’, ‘nice game’); // … Read more
Getting the ball rolling with this community wiki answer. Feel free to edit me with your improvements. ws WebSocket server and client for node.js. One of the fastest libraries if not the fastest one. websocket-node WebSocket server and client for node.js websocket-driver-node WebSocket server and client protocol parser node.js – used in faye-websocket-node faye-websocket-node WebSocket … Read more
Misconceptions There are few common misconceptions regarding WebSocket and Socket.IO: The first misconception is that using Socket.IO is significantly easier than using WebSocket which doesn’t seem to be the case. See examples below. The second misconception is that WebSocket is not widely supported in the browsers. See below for more info. The third misconception is … Read more