套接字 IO 服务器到服务器

Question

Is it possible for a server to connect to another using Socket.IO and be treated like a client?

And have it join rooms, recieve io.sockets.in('lobby').emit(). And more?

The first server is also listening for connections/messages as well.

Hey Brad, here's my full .js app below for reference:

var io = require("socket.io").listen(8099);
io.set('log level', 1);

io.sockets.on("connection", function (socket) {

    console.log('A Client has Connected to this Server');

    //Let Everyone Know I just Joined   
    socket.broadcast.to('lobby').emit("message",'UC,' + socket.id); // Send to everyone in Room but NOT me  


socket.on("message", function (data) {

//Missing code
socket2.send('message,' + data); //Forward Message to Second Server

});

socket.on("disconnect", function (data) {
    //Send Notification to Second Server
    //Need to figure out later

    //Send Notification to Everyone
    socket.broadcast.emit("message",'UD,' + socket.id ); //Send to Everyone but NOT me

    //Remove user from Session ID
    arSessionIDs.removeByValue(socket.id);      

    //Send Notification to Console
    console.log("disconnecting " + arRoster[socket.id][1]);
});

});

var io_client = require( 'socket.io-client' );
var socket2 = io_client.connect('http://192.168.0.104:8090');
socket2.on('connect', function () {
socket2.emit('C3434M,Test');
});

Answer 1

Yes, absolutely. Just use the Socket.IO client in your server application directly.

https://github.com/LearnBoost/socket.io-client

You can install it with npm install socket.io-client . Then to use:

var socket = io.connect('http://example.com');
socket.on('connect', function () {
  // socket connected
  socket.emit('server custom event', { my: 'data' });
});

Answer 2

I realize this is an old post, but I was working on something similar and decided to come back and contribute something as it got me thinking.

Here's a basic Client -> Server 1 -> Server 2 setup

Server #1

// Server 1
var io = require("socket.io").listen(8099); // This is the Server for SERVER 1
var other_server = require("socket.io-client")('http://example.com:8100'); // This is a client connecting to the SERVER 2

other_server.on("connect",function(){
    other_server.on('message',function(data){
        // We received a message from Server 2
        // We are going to forward/broadcast that message to the "Lobby" room
        io.to('lobby').emit('message',data);
    });
});

io.sockets.on("connection",function(socket){
    // Display a connected message
    console.log("User-Client Connected!");

    // Lets force this connection into the lobby room.
    socket.join('lobby');

    // Some roster/user management logic to track them
    // This would be upto you to add :)
    
    // When we receive a message...
    socket.on("message",function(data){
        // We need to just forward this message to our other guy
        // We are literally just forwarding the whole data packet
        other_server.emit("message",data);
    });
    
    socket.on("disconnect",function(data){
        // We need to notify Server 2 that the client has disconnected
        other_server.emit("message","UD,"+socket.id);
        
        // Other logic you may or may not want
        // Your other disconnect code here
    });
});

And here's Server #2

// Server 2
var io = require("socket.io").listen(8100);
io.sockets.on("connection",function(socket){
    // Display a connected message
    console.log("Server-Client Connected!");
    
    // When we receive a message...
    socket.on("message",function(data){
        // We got a message. I don't know, what we should do with this
    });
});

This is our Client, who sends the original message.

// Client
var socket = io('http://localhost');
socket.on('connect', function(){
    socket.emit("message","This is my message");
    
    socket.on('message',function(data){
        console.log("We got a message: ",data);
    });
});

I am making this post a Community Wiki so that someone can improve this if they feel like it.

The code has not been tested, use at your own risk.

Answer 3

I had the same problem, but instead to use socket.io-client I decided to use a more simple approach (at least for me) using redis pub/sub, the result is pretty simple.

You can take a look at my solution here: https://github.com/alissonperez/scalable-socket-io-server

With this solution you can have how much process/servers you want (using auto-scaling solution), you just use redis as a way to forward your messages between your servers.