|
if you were to implement this though, my suggestion is this:
Use the concept of Browse Masters in MS Networks. You would follow these basic rules:
At login you query the channel to find out who the browse master is.
If none reply, you become the new master.
If one does reply, that user is given master in your session.
When you request data, you check your own entries.
If the data is not present locally, you query the data master.
If the data master cannot provide the info, a new master election is called.
Clients query local tables, and also query total tables.
The client with the answer, and the most total tables becomes master.
New master responds with answer to original query.
---------------------------------------------------------------------------------------
It seems like a lot of work, and it may be. But it would also reduce the number of responses considerably and thus reduce bandwidth strain as well...
I hope that made sense...
|