[Spread-users] Spread Configuration

Wangbong Lee leewb at etri.re.kr
Fri Jun 1 04:19:58 EDT 2007

Thanks for your reply. 

Here is sample configuration with 3 nodes(A,B,C) in same network domain (not
through router).
With your comments, as I understood, possible one configuration is;
A "local" daemon and a "remote" daemon can run node A, and a "local" daemon
can run each B and C. 
In your comments, the daemons in each nodes can communicate each other. I
wonder, what information
is delivered among them? 

Other question is about "no network bandwidth is consumed in local
In your words, if the client's connection is local, then the client-daemon
communication remains
 within the machine -- no network bandwidth is consumed. However, when I
tested local messaging 
within the machine, those messages are out to physical interface. (I
tcpdumped those packets.)
Thus, meaning of "no network bandwidth is consumed" is not clear.  Could you
tell me about that more?


> -----Original Message-----
> From: spread-users-bounces at lists.spread.org [mailto:spread-users-
> bounces at lists.spread.org] On Behalf Of John Schultz
> Sent: Friday, June 01, 2007 1:20 AM
> To: Spread-users at lists.spread.org
> Subject: RE: [Spread-users] Spread Configuration
> On Thu, 31 May 2007, Wangbong Lee wrote:
> > If you ran a daemon on every computer that had clients, then a clients
> send
> > would translate to a single reliable broad/multicast sent between the
> > daemons.
> >   All the client communication would be contained within the machines.
> >
> > What do you mean by that?
> > You mean that the clients have to communicate each daemon for
> distributed
> > computing
> > instead of connecting one daemon in its machine ?
> No, each client only connects to a single daemon.  That daemon then acts
> as the client's "representative" within the communication system and
> performs the necessary actions to serve the client's needs.
> A client's connection can either be to a "local" daemon on the same
> machine using Inter Process Communicaiton, or it can be to a "remote"
> daemon on another machine using TCP/IP.  If the client's connection is
> local, then the client-daemon communication remains within the machine --
> no network bandwidth is consumed.  If the client's connection is remote,
> then the client-daemon communication goes over the network.
> > Other question, is it possible to communicate between daemons ?
> Yes, when you place multiple daemons within the same configuration file
> (e.g. - spread.conf), then those daemons will work together to form a
> distributed communication system.  Clients that then connect to any of
> those daemons will have access to the clients connected to all the
> currently connected daemons in that configuration.

> Here is a good place to start reading:
> http://www.spread.org/docspread.html
> Cheers!
> ---
> John Schultz
> Spread Concepts
> Phn: 443 838 2200
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users

More information about the Spread-users mailing list