|
While for a small network this may not be an issue, if you were to get a lot of people doing it all at once, it would be a lag nightmare.
With all the methods discussed so far everything is still done in a channel.
For example let's say you have 50 users. All with a decent connection, so we'll assume about 2 seconds to pass the token, and either respond or pass. That means about 1:40 to do a search (assuming no one has the answer) and 50 messages.
50 messages in almost two minutes probally isn't that bad. Now what if two people search at the same time? You've doubled both the time to search and the amount of spam in the channel. I'm guessing that by the time you get up to four or five searches, it would be enough to start causing lag.
What might be better is if the channel instead handled updates. Every so often (maybe two or three hours) a client would offer an update (offer, not request) Then anyone who wanted the update (people who haven't updated in 12 hours) would join the channel and recieve the new data.
|