Update To completely remove debugging use: var io = require(‘socket.io’).listen(app, { log: false }); Where app is node.js http server / express etc. You forgot to mention you are also using socket.io. This is coming from socket.io. You can disable this by configuration: io.set(‘log level’, 1); // reduce logging
io.sockets.emit will send to all the clients socket.broadcast.emit will send the message to all the other clients except the newly created connection This Socket.IO Wiki post will help everyone reading this question: The recent cheatsheet can also be viewed here: https://socket.io/docs/v4/emit-cheatsheet
You can use socket.io rooms. From the client side emit an event (“join” in this case, can be anything) with any unique identifier (email, id). Client Side: var socket = io.connect(‘http://localhost’); socket.emit(‘join’, {email: user1@example.com}); Now, from the server side use that information to create an unique room for that user Server Side: var io = … Read more
socket.broadcast.to broadcasts to all sockets in the given room, except to the socket on which it was called while io.sockets.in broadcasts to all sockets in the given room.
Edit: I feel it’s better for anyone to consult the excellent chat example on the Socket.IO getting started page. The API has been quite simplified since I provided this answer. That being said, here is the original answer updated small-small for the newer API. index.html <!doctype html> <html> <head> <script src=”https://stackoverflow.com/socket.io/socket.io.js”></script> <script> var socket = … Read more
I finally managed to do it, thanks to this topic. TODO: 1) Have Apache 2.4 installed (doesn’t work with 2.2), and do: a2enmod proxy a2enmod proxy_http a2enmod proxy_wstunnel 2) Have nodejs running on port 3001 3) Do this in the Apache config <VirtualHost *:80> ServerName example.com RewriteEngine On RewriteCond %{REQUEST_URI} ^/socket.io [NC] RewriteCond %{QUERY_STRING} transport=websocket … Read more
Edit: This is now possible You can now simply call socket.disconnect() on the server side. My original answer: This is not possible yet. If you need it as well, vote/comment on this issue.
Use connect-redis and have redis as your session store for all authenticated users. Make sure on authentication you send the key (normally req.sessionID) to the client. Have the client store this key in a cookie. On socket connect (or anytime later) fetch this key from the cookie and send it back to the server. Fetch … Read more
That should be possible using Socket.IO-client: https://github.com/LearnBoost/socket.io-client
Okay, as of 0.7.7 this is available, but not in the manner that lubar describes. I ended up needing to parse through some commit logs on git hub to figure this one out, but the following code does actually work for me now: var io = require(‘socket.io’).listen(server); io.sockets.on(‘connection’, function (socket) { var address = socket.handshake.address; … Read more