a drop-in replacement for node's net module that works in a sane way when clustered
npm install net-clusternet-cluster
===========
``javascript`
server.listen(0)
http://nodejs.org/api/cluster.html
from the documentation:
> Normally, this will case servers to listen on a random port. However, in a cluster, each worker will receive the same "random" port each time they do listen(0). In essence, the port is random the first time, but predictable thereafter. If you want to listen on a unique port, generate a port number based on the cluster worker ID.
`javascript``
/**
* uses net-cluster instead of net to create a server
*
* Note: 2 servers will be created and they will be listening
* on 2 distinct random ports. Try using node's net module instead
* of net-cluster and see what happens.
*/
var cluster = require('cluster')
, net = require('net-cluster')
;
if (cluster.isMaster) {
cluster.fork();
cluster.fork();
} else if (cluster.isWorker) {
var server = net.createServer();
server.listen(function() {
var port = server.address().port;
console.log('listening on port: ' + port);
});
}