AW: [IRCServices Coding] session limit bug

[Georges Berscheid]

If you want to resynchronize services (which was the starting point of 
this discussion, as far as I remember), you will have to flush services 
databases kept in memory, before synchronizing, to make sure you really 
get to exactly the same state as your uplink server.
But, this means you lose all information you had so far. (E.g. you must 
clear channel modes on resynchronization, because you assume you don't 
know the correct ones, and refetch them from your uplink server.)
I'll stop the discussion at this point, because IMO it's really the 
wrong approach to handle this problem.

Georges



V13 wrote:

>On Monday 24 March 2003 20:22, Georges Berscheid wrote:
>  
>
>>Hi,
>>
>>the requested command exists: /os restart
>>How do you think services could possibly make the uplink send all the
>>information again, as if services just joined the network? This
>>'simulated-net-merge-situation' would have to be supported by the
>>uplink-IRCd.
>>    
>>
>
>I know that this is complicated but if services could squit and reconnect 
>themselves without restarting would be great. This whould prevent all kind of 
>notices they send to users and they will not require users to identify 
>themselves or reset modes to channels etc... 
>
>This can be almost transparent to the entire network.
>
>  
>
>>Georges
>>    
>>
><<V13>>
>
>
>
>  
>