Please add some sort of netsplit detection to stop the WALL OF TEXT
#1 Updated by EgS about 13 years ago
Detecting a netsplit is somewhat easy... what is difficult is:
when a netsplit occurs the server sends one quit message per user. We would have to buffer those messages until the last one is sent, so we can remove the users as a bulk. The question is: which one is the last quit message?
#3 Updated by Sputnick over 12 years ago
- Status changed from New to Confirmed
Question is we need to bulk-remove the users, or if just not showing the messages is already enough to fix the performance issue. To detect the end of it, one could probably just use a timeout (a second or so should be enough, since I assume that the QUIT msgs are sent en-block by the server) and then send a summary message to inform the GUI.
#5 Updated by seezer about 12 years ago
- % Done changed from 0 to 90
Coreside work is done. For the clientside representation, I'll wait for the new fancy styling stuff to be merged into master. So you'll get pretty raw messages - but only one join/quit for each netsplit.
Work is done in my netsplit branch available at:
Note that the branch will be rebased after Sput's styling magic hit master.