1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> AW: [IRCServices Coding] session limit bug
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%20Coding%5D%20session%20limit%20bug&In-Reply-To=">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"001998.html">
11 <LINK REL=
"Next" HREF=
"002000.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>AW: [IRCServices Coding] session limit bug
</H1>
15 <B>Georges Berscheid
</B>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%20Coding%5D%20session%20limit%20bug&In-Reply-To="
17 TITLE=
"AW: [IRCServices Coding] session limit bug">georges at berscheid.lu
19 <I>Wed Mar
26 08:
22:
59 PST
2003</I>
21 <LI>Previous message:
<A HREF=
"001998.html">AW: [IRCServices Coding] session limit bug
23 <LI>Next message:
<A HREF=
"002000.html">AW: [IRCServices Coding] session limit bug
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#1999">[ date ]
</a>
27 <a href=
"thread.html#1999">[ thread ]
</a>
28 <a href=
"subject.html#1999">[ subject ]
</a>
29 <a href=
"author.html#1999">[ author ]
</a>
34 <PRE>If you want to resynchronize services (which was the starting point of
35 this discussion, as far as I remember), you will have to flush services
36 databases kept in memory, before synchronizing, to make sure you really
37 get to exactly the same state as your uplink server.
38 But, this means you lose all information you had so far. (E.g. you must
39 clear channel modes on resynchronization, because you assume you don't
40 know the correct ones, and refetch them from your uplink server.)
41 I'll stop the discussion at this point, because IMO it's really the
42 wrong approach to handle this problem.
50 ><i>On Monday
24 March
2003 20:
22, Georges Berscheid wrote:
55 </I>>><i>the requested command exists: /os restart
56 </I>>><i>How do you think services could possibly make the uplink send all the
57 </I>>><i>information again, as if services just joined the network? This
58 </I>>><i>'simulated-net-merge-situation' would have to be supported by the
59 </I>>><i>uplink-IRCd.
63 </I>><i>I know that this is complicated but if services could squit and reconnect
64 </I>><i>themselves without restarting would be great. This whould prevent all kind of
65 </I>><i>notices they send to users and they will not require users to identify
66 </I>><i>themselves or reset modes to channels etc...
68 </I>><i>This can be almost transparent to the entire network.
72 </I>>><i>Georges
75 </I>><i><<V13
>>
90 <LI>Previous message:
<A HREF=
"001998.html">AW: [IRCServices Coding] session limit bug
92 <LI>Next message:
<A HREF=
"002000.html">AW: [IRCServices Coding] session limit bug
94 <LI> <B>Messages sorted by:
</B>
95 <a href=
"date.html#1999">[ date ]
</a>
96 <a href=
"thread.html#1999">[ thread ]
</a>
97 <a href=
"subject.html#1999">[ subject ]
</a>
98 <a href=
"author.html#1999">[ author ]
</a>