Is it possible to set up a socket.io client runnin

Question

I'd like to enable socket-based p2p communications between two or more different node.js application servers. I'm using socket.io to handle all such communication between a given server and the web application it serves - but what I'm looking for is a way to communicate server-to-server.

I had initially assumed it would be as easy as something like this:

var io = require("socket.io");
var socket = io.connect("my remote endpoint");

However, as it turns out the server-side socket.io implementation doesn't offer a "connect" method, only a listen method.

Why is this? Why can't I treat a node application server as a client to a socket.io server running elsewhere? Is there any way that I can achieve this functionality?

Answer 1

Before you go full speed on socket.io for server-to-server communications..... socket.io is engineered as a browser to server comm infrastructure. I'm far from certain it is the best solution for P2P server stuff. Plus, if you do server-to-server - why not just do Websockets? There are various websocket modules for node - e.g. https://github.com/einaros/ws

Answer 2

Just for clarification, this is an example with listeners and possibility to emit events (and without install again a module already installed)

var io = require('socket.io/node_modules/socket.io-client');

client = io.connect('http://'+CONFIG.host+':'+CONFIG.port);

client.on('connect',function() {
    client.emit("test","foo");
}); 

Answer 3

OK, so thanks to @pimvdb in the comments above I've got a workable solution.

Basically, the socket.io library that npm installs has a dependency on another module, called socket.io-client. In a standard socket.io installation this will be installed in node_modules/socket.io/node_modules/socket.io-client

However, it's also possible to say "npm install socket.io-client" and install it as its own first-class citizen library.

Then your usage looks like this:

var client = require("socket.io-client");
client.connect("http://myendpoint.com:3000/whatever");
client.emit("test", "foo");

And everything works.

So, thanks man!