No tutorial needed. The Socket.IO FAQ is pretty straightforward on this one: socket.emit(‘news’, { hello: ‘world’ }); EDIT: Folks are linking to this question when asking about how to get that socket object later. There is no need to. When a new client connects, save a reference to that socket on whatever object you’re keeping … Read more
Find your server.listen call and change the port from 3000 to 80. Don’t forget that you have to run the program with the CAP_NET_BIND_SERVICE capability (see capabilities(7) for details) in order to bind to ports less than 1024 on Linux systems. root privilege will contain this, and other, privileges.
The short answer: io.sockets.adapter.rooms I analysed io: I got the following output: { server: { stack: [ [Object], [Object], [Object], [Object], [Object], [Object] ], connections: 3, allowHalfOpen: true, watcher: { host: [Circular], callback: [Function] }, _events: { request: [Function], connection: [Function: connectionListener], listening: [Object], upgrade: [Object] }, httpAllowHalfOpen: false, cache: {}, settings: { home: “https://stackoverflow.com/”, … Read more
There is a project on codeplex ( NuGet as well ) that is a C# client for socket.io. (I am the author of this project – so I’m biased) I couldn’t find exactly what I needed in a client, so I built it and released it back into the open. Example client style: socket.On(“news”, (data) … Read more
For future people: Here is 2 very simple Node.js apps that use socket.io to connect, send and receive messages between each other. Required package is: npm install socket.io Node-App-1 server.js: var io = require(‘socket.io’).listen(3000); io.on(‘connection’, function (socket) { console.log(‘connected:’, socket.client.id); socket.on(‘serverEvent’, function (data) { console.log(‘new message from client:’, data); }); setInterval(function () { socket.emit(‘clientEvent’, Math.random()); … Read more
After further poking and prodding, I found some incredibly useful information. In the author’s example, he points out the critical step of establishing socket listeners in the before hooks. This example works: Assuming a server is listening for socket connections at localhost:3001, of course var io = require(‘socket.io-client’) , assert = require(‘assert’) , expect = … Read more
It’s not actually sending an update to the other clients at all, instead it’s just emitting to the client that just connected (which is why you see the update when you first load) // socket is the *current* socket of the client that just connected socket.emit(‘users_count’, clients); Instead, you want to emit to all sockets … 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.
Here’s my solution for the following environment: express 4.2.0 socket.io 1.1.0 cookie-parser 1.0.1 cookie-session 1.0.2 Code: var cookieParser = require(‘cookie-parser’)(); var session = require(‘cookie-session’)({ secret: ‘secret’ }; … app.use(cookieParser); app.use(session); … io.use(function(socket, next) { var req = socket.handshake; var res = {}; cookieParser(req, res, function(err) { if (err) return next(err); session(req, res, next); }); }); … Read more
The Issues First of all you need to be looking at the server port that the server is bound on (app.listen(3001);) on the client side in order to reach the server at all. As for socket.io, adding http://localhost:3001 before the rest of the source in the link tag solves this problem. This is apparently due … Read more