]> jfr.im git - irc.git/blob - software/RELEASES/ircservices/achurch.org/services/lists/ircservices-coding/2003/001999.html
rename -> *.git
[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2003 / 001999.html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
2 <HTML>
3 <HEAD>
4 <TITLE> AW: [IRCServices Coding] session limit bug
5 </TITLE>
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">
12 </HEAD>
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
18 </A><BR>
19 <I>Wed Mar 26 08:22:59 PST 2003</I>
20 <P><UL>
21 <LI>Previous message: <A HREF="001998.html">AW: [IRCServices Coding] session limit bug
22 </A></li>
23 <LI>Next message: <A HREF="002000.html">AW: [IRCServices Coding] session limit bug
24 </A></li>
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>
30 </LI>
31 </UL>
32 <HR>
33 <!--beginarticle-->
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.
43
44 Georges
45
46
47
48 V13 wrote:
49
50 &gt;<i>On Monday 24 March 2003 20:22, Georges Berscheid wrote:
51 </I>&gt;<i>
52 </I>&gt;<i>
53 </I>&gt;&gt;<i>Hi,
54 </I>&gt;&gt;<i>
55 </I>&gt;&gt;<i>the requested command exists: /os restart
56 </I>&gt;&gt;<i>How do you think services could possibly make the uplink send all the
57 </I>&gt;&gt;<i>information again, as if services just joined the network? This
58 </I>&gt;&gt;<i>'simulated-net-merge-situation' would have to be supported by the
59 </I>&gt;&gt;<i>uplink-IRCd.
60 </I>&gt;&gt;<i>
61 </I>&gt;&gt;<i>
62 </I>&gt;<i>
63 </I>&gt;<i>I know that this is complicated but if services could squit and reconnect
64 </I>&gt;<i>themselves without restarting would be great. This whould prevent all kind of
65 </I>&gt;<i>notices they send to users and they will not require users to identify
66 </I>&gt;<i>themselves or reset modes to channels etc...
67 </I>&gt;<i>
68 </I>&gt;<i>This can be almost transparent to the entire network.
69 </I>&gt;<i>
70 </I>&gt;<i>
71 </I>&gt;<i>
72 </I>&gt;&gt;<i>Georges
73 </I>&gt;&gt;<i>
74 </I>&gt;&gt;<i>
75 </I>&gt;<i>&lt;&lt;V13&gt;&gt;
76 </I>&gt;<i>
77 </I>&gt;<i>
78 </I>&gt;<i>
79 </I>&gt;<i>
80 </I>&gt;<i>
81 </I>
82
83
84 </PRE>
85
86 <!--endarticle-->
87 <HR>
88 <P><UL>
89 <!--threads-->
90 <LI>Previous message: <A HREF="001998.html">AW: [IRCServices Coding] session limit bug
91 </A></li>
92 <LI>Next message: <A HREF="002000.html">AW: [IRCServices Coding] session limit bug
93 </A></li>
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>
99 </LI>
100 </UL>
101
102 </body></html>