That couldnt have been simpler - I already use Redis for RMI/RPC…now I can use it to cluster socket.io? Best! :) Thanks for the link.
On Sa. Apr. 11 2015 19:39:14 Guillermo Rauch wrote: > Check this out: > http://socket.io/docs/using-multiple-nodes/#passing-events-between-nodes > <http://socket.io/docs/using-multiple-nodes/#passing-events-between-nodes> > > — > @rauchg <https://twitter.com/rauchg> > On Sat, Apr 11, 2015 at 10:36 AM Kevin Ingwersen (Ingwie Phoenix) > <[email protected] <mailto:[email protected]>> wrote: > Hey. > > So now that I have a plan for scaling my Express app, I am likely going to > give my Socket.io service the same treat. But there is a little bit of a > concern I have. > > Say I have 2 workers for a chat service. A good way to promote that a user > logged in is to broadcast to all sockets connected…but how exactly will this > work if worker#1 sends the broadcast - will worker#2’s sockets also be > affected? I dont know if cluster.fork()’ed processes share the sockets or not… > > Kind regards, > Ingwie -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/05DB7D57-623F-4A21-9021-DFD90860A695%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
