Sharing socket.io servers/connections

[jskulski]

Hey,

Been playing around with juggernaut for a bit, I like it and saved me a bunch of work so thanks.

I have webapp that has some pub/sub data that gets pushed to clients. That's where juggernaut comes in.
I also have non-pubsub data, like list of channels or archived deals. I'm new to this, so its quite possible I just have a wrong idea or architecture. That's why I'm checking ;)

Is there anyway to:

• tell juggernaut a socket.io server to use?
• piggyback on juggernaut's socket.io server?
• use juggernaut for non/pub data?

The other method I could think of is that I have a 'all' channel that every connection connects to and I can publish to that, but that seems wasteful, both in having to spin through all the subscribers and also pushing it through redis instead of directly through socket.io.

I'll keep looking, but let me know if you have any ideas.

[jskulski]

I am using node.js as the backend if that wasn't clear. Thanks!

[simplyb]

I'm using Rails 3 and I configure the redis server to connect to with this code in an initializer:

Then in JavaScript I configure which juggernaut server to connect to:

var options = {
        host: host,
        secure: secure,
        port: port
};
MyApp.juggernaut = new Juggernaut(options);