Allow multiple listeners to be bound to a server

[johnboxall]

I've have two distinct types of connections coming at my server - it would seem the easiest way to separate them would be to bind create two io.listeners and change the resource of each connection type - however in the current implementation in Listener.init will just grab the last Listener bound to the server!

p.s Fantastic piece of software!

[johnboxall]

Meant to leave this on Socket.IO-node

[rauchg]

Are you saying you have two HTTP servers, or you have two widgets that need realtime connectivity in the same page? If the answer is the latter, you have to build a small protocol on top of a single io.Listener to channel the messages.

At LearnBoost, we built a simple channel-subscription model tied to server side and client side event listeners, so that we can have several independent flows of communication, but with only 1 transport initialization per client.

[johnboxall]

I'm working on a remote JavaScript debugger - on one page, you've got a console. On the other page the debugger is running.

Whenever a debugger connects it opens a new channel. Consoles connect to a debugger channel to receive messages. Debuggers send messages to all connected consoles.

I could use conditional logic inside the connection/message event listeners, it would seem more DRY to create multiple listeners and have the correct one fire by inspecting the "resource".

io.listen(server, {
    resource: "socket.io.console",
    onClientMessage: function(message, client){
        sys.puts("Client Message!");
    }
});

io.listen(server, {
    resource: "socket.io.debugger",
    onClientMessage: function(message, client){
        sys.puts("Debugger Message!");
    }
});

// Vs.

io.listen(server, {
    onClientMessage: function(message, client){
        if (message.type == "client"){
            sys.puts("Client Message!");
        } else{
            sys.puts("Debugger Message!");        
    }
});

// ++ Extra logic in the client for constructing the message.