From: Dominic Tarr <dominic.t...@gmail.com>
Date: Wed, 12 Sep 2012 23:47:54 +0200
Local: Wed, Sep 12 2012 5:47 pm
Subject: Re: [nodejs] Re: best practice for real-time socket-based cross clustered-process data communication and computation
You need to make every "client" a tcp server.
if they live on the same machine, use a unix socket instead of a port number.
see the docs for "net".
Obviously, each node will need to keep track of every other node it
Also, what kind of messages are they sending?
On Tue, Sep 11, 2012 at 10:21 AM, Yi Tan <yi2...@gmail.com> wrote:
> Thanks Johnny,
> dnode is very inspiring. cluster2 may help us a lot in production!
> 2012/9/11 Johnny Honestly <mostmodern...@gmail.com>
>> I heard about this cluster manager today directly from the guys at ebay
>> You can stream buffers from parents to child process using stdin/out
>> If you need sockets try dnode
>> On Monday, September 10, 2012 1:45:12 AM UTC-7, Yi wrote:
>>> Hi node mates:
>>> I'm looking for your advice about how to design and implement an
>>> [The server layout]
>>> clientA <--tcp socket--> node service A <--> DataModelA <--> unique radis
>>> clientB <--tcp socket--> node service B <--> DataModelB <--> unique radis
>>> * node service A and B are cluster on the same server
>>> [The function request]
>>> I need to implement a mechanism, in which:
>>> the logic looks like the following diagram:
>>> clientA <--tcp socket--> node service A
>>> Do you know what is the best way to do this, or is there something
>>> Many thanks,
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.