[Konversation-devel] [Bug 116541] server split leave and join events

david powell achiestdragon at gmail.com
Wed Sep 10 12:41:46 CEST 2008


http://bugs.kde.org/show_bug.cgi?id=116541





--- Comment #5 from david powell <achiestdragon gmail com>  2008-09-10 12:41:44 ---
seems i posted this some time back 
but heres what i spotted 

it should be possible to fix this as 

when a nick  joins ie 

 Join ChanServ has joined this channel (ChanServ at services.).

the bracketed section provides its "native server"
usualy that would also be the same on a quit
although  (remote closed connection ) is also valid for quit

but during a netsplit  all parties involved in the split  part with a 

Quit ChanServ has left this server (heinlein.freenode.net irc.freenode.net).

where the bracketed  data is indicating the server that has broken its
connection 

given this i should be possible to check the parting server address 
compaire it to the server info that is associated with the nick 
and flag that nick in the list as  temp broken  rather than displaying it as 
parted ,, then re enabling it once a join of that nick is received 

although thinking about this  the following seems a better way to handle it 
when a nick parts  dew to a netsplit  detected by the above method 
dump the affected nicks into a (temp list (not displayed)) remove it from the
nick list for the chan , announce a message >>netsplit (server.name)!!  or
something to that effect 
when a nick then rejoins if its in the temp list just add it back to the main
chan nick list without generating any notification 
would guess that just a simple time stamp on the nicks in the temp list should
be fine with say those in it over 2hrs just get removed , so that if they
rejoin then it will announce there return as normal 

that would also  prevent it dumping the whole list if one of the users
reconnects via a diferent server during a split


Dave


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Konversation-devel mailing list