[Spread-users] spread communication between segments
jschultz at spreadconcepts.com
Fri May 21 12:04:50 EDT 2004
The order of daemons listed in your configuration file determines two
important things: (1) which daemon within a segment is the
representative (defined below) and (2) the order that the control token
travels around the daemon token ring.
Once a daemon membership/view is installed, within a segment/site the
first daemon listed in the conf. file that is participating is the
representative. The representative is responsible for receiving msgs
from other segments and distributing them "locally" within the segment
When any daemon needs to send a message it *casts it "locally" and then
sends the message directly to each of the other segments/sites
The control token is sent by unicast in the order of the configuration
file listing to the daemons that are participating. The last
participating daemon in a segment sends the token to the representative
of the next segment in the conf. file. Representatives get the token
from the last participating daemon in the previous segment of the conf.
file. After they send any messages the token is passed to the next
participating daemon listed in the conf. file and so on.
John Lane Schultz
Spread Concepts LLC
Phn: 443 838 2200
Greg Shebert wrote:
> hi folks
> how does spread determine which daemons in different segments will be
> the ones that communicate messages between those segments?
> do all daemons in a segment get involved or just certain ones?
> i'm curious to know for the purpose of loading on various daemons
> Spread-users mailing list
> Spread-users at lists.spread.org
More information about the Spread-users