Implement a channel between nodes without a central server?

[andrew-kennedy]

I'd like to allow nodes to communicate without needing to use redis or sockets.io, is there a recommended way to do this in gaggle, assuming I have the IPs of the nodes?

[ben-ng]

I haven't written a channel like that yet, but it's totally doable.

1. Duplicate an existing channel and name it p2p-channel or something like that.
2. Modify the options so that the user can specify what nodes are in the cluster.
3. Use net.socket (docs) or similar to send & receive messages.

[andrew-kennedy]

thank you! I just now noticed the channel-interface file. I'll look into it.

[andrew-kennedy]

I noticed something else, in the readme you use a channel with name: redis, and redisName: foo, but then later have a channel with name: redis and channelName: foo. Is there a reason for this distinction/naming convention? what's the difference between the channelName and the name?

[andrew-kennedy]

@ben-ng I'm sort of new to node.js programming, would the p2p channel effectively need to start a TCP server in the constructor so that each node has a server? And then in the _connect method there would be logic connecting to each node? I'm just a bit confused as to how the concept of a Channel maps to a bunch of nodes. Each example channel connects to one external service at the moment.

[ben-ng]

Yes, the channel would start a server and then connect to each node.

[ben-ng]

Closing in favor of #12