|
I would maybe also suggest not making all clients sinc to the same data as the others. In other words, if you log in and there is a master, and the master has more tables than you, you don't automatically get all the data he has. This would take a lot of bandwidth and time depending on how much more data he has than you.
You COULD maybe add a "data sync" button that queries for a dump of the data tables from the master. Only the person that queries for the sync actually gets updated. That way you aren't locking 100+ people up in the middle of whatever they are doing as their client listens and responds to hundreds of data tables being pushed through chat.
This would involve a listening engine that basically uses a toggle. It listens in a specific chat channel, and if query is set to on, it will collect data. If query is set to off, it will not. Browse masters always have query set to on, because they have to respond to queries. If you ask something, your query variable gets set to on, so you can listen for the answer, and as soon as the answer is recieved, it gets toggled off. Master Elections automatically enabled query to be toggled on for everyone for the duration of the election, and also disabled active querying for all clients until the election is finished...
|