master server redundancy/improvements
I always thought the masters contacted eachother to keep a fresh list of servers just in case one goes down.
This is not the case as Manc pointed out and if we are going to have multiple masters running, we should do this.
So, masters should contact eachother, but only if they are on an "official" list of addresses, a whitelist.
Also, make the max number of servers optional, maybe a master server host wants more than 1024? there's also max server per IP, maybe this can be made changeable also and possibly allow exceptions to the rule.
this is a dupe of bug 254
if masters contact each other, the following will happen:
a) complexity of code will become unmanageable
b) redundancy is reduced as a faulty/stuck/attacked list on one will propagate to the other
i am very concerned about both, and think our current master works quite well already
if we want to see all entries, maybe this is better off being done as a merge of received lists on the launcher?
> if we want to see all entries, maybe this is better off being done as a merge
> of received lists on the launcher?
This is done already
Can't believe we didn't notice this before, duplicate of 254.
*** This bug has been marked as a duplicate of bug 254 ***