[Spread-users] Connecting spread daemons with different segment configurations

[Timo Korthals]

Dear Spread users,

we are using spread daemons for our distributed robot network.
We know already, that each device needs exact the same configuration 
regarding the segments, otherwise the spread daemons wont connect to 
each other.
But is there a way to not have the same segment configurations?
So lets assume the following scenario of three participants {1,2,3}.

*1. is a server, which knows the participants 2 and 3*
/spreadOne.conf:/
Spread_Segment  192.168.0.255:4803 {
         one               192.168.0.1
}
Spread_Segment  192.168.0.255:4803 {
         two               192.168.0.2
}
Spread_Segment  192.168.0.255:4803 {
         three               192.168.0.3
}

*2. and 3. are just clients, which are allowed to talk with the server, 
but not with each other*
/spreadTwo.conf:/
Spread_Segment  192.168.0.255:4803 {
         one               192.168.0.1
}
Spread_Segment  192.168.0.255:4803 {
         two               192.168.0.2
}

/spreadThree.conf:/
Spread_Segment  192.168.0.255:4803 {
         one               192.168.0.1
}
Spread_Segment  192.168.0.255:4803 {
         three               192.168.0.3
}


Obviously this does not work with spread, am I right?
But if so, how can I make it work?
Is spread just comparing the hashes of the configs, and refusing 
connections, if hashes mismatch?
What happens if I remove the checks regarding the configuration check?
Has anyone done this before?

Greetings,
Timo

-- 

Timo Korthals, M.Sc.
Universität Bielefeld
AG Kognitronik & Sensorik
Exzellenzcluster Cognitive Interaction Technology (CITEC)
Inspiration 1 (Zehlendorfer Damm 199)
33619 Bielefeld - Germany

Office  : 3.037
Phone   : +49 521 106-67368
eMail   : tkorthals at cit-ec.uni-bielefeld.de
Internet: http://www.ks.cit-ec.uni-bielefeld.de/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.spread.org/pipermail/spread-users/attachments/20150129/940fc0ca/attachment.html