1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] Ideas , features
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Ideas%20%2C%20features&In-Reply-To=Pine.LNX.4.33.0103141607030.25228-100000%40darkness.darkness.gr">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"001605.html">
11 <LINK REL=
"Next" HREF=
"001600.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] Ideas , features
</H1>
15 <B>Yusuf Iskenderoglu
</B>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Ideas%20%2C%20features&In-Reply-To=Pine.LNX.4.33.0103141607030.25228-100000%40darkness.darkness.gr"
17 TITLE=
"[IRCServices] Ideas , features">uhc0 at rz.uni-karlsruhe.de
19 <I>Thu Mar
15 00:
11:
01 PST
2001</I>
21 <LI>Previous message:
<A HREF=
"001605.html">[IRCServices] Ideas , features
23 <LI>Next message:
<A HREF=
"001600.html">[IRCServices] Nick Identification bug?
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#1607">[ date ]
</a>
27 <a href=
"thread.html#1607">[ thread ]
</a>
28 <a href=
"subject.html#1607">[ subject ]
</a>
29 <a href=
"author.html#1607">[ author ]
</a>
36 I do not see, why this idea has to be denied right from the beginning.
37 I personally see this useful, because:
40 - The current implementation might be expanded, to include the map of the
41 network, in a way that services manages a structure for each server, to
42 see who is linked to whom, etc.
44 - This can be used to implement Bahamut's NOQUIT, because, that way,
45 services WILL know, which nicknames have quit due to a split, without
46 needing to see the quit message from the hub it is connected.
48 - This can be / is being used to implement the StatServ's MAP command
51 - This can also be used in a timer event, as described, to maintain the
52 linkage. The reality, that the linking had to occur automatically, is of
53 course wanted, but never realised effectively. I can tell from own
54 experience, where our hub is not configured to send a connect itself, but
55 is designed to wait for connects. This way, the server is not keeping
56 track of who was disconnected, or whether it should connect, etc.
57 If services itself sent the connect command, because it saw the squit, it
58 would of course be managed quicker. I do not see, why some of us are
59 declaring this as a non-capable administration.
64 On Wed,
14 Mar
2001 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">dreamer at darkness.gr
</A>
67 ><i> Greetings all,
68 </I>><i> I had an idea long time ago, i think that the list is appropriate
69 </I>><i> to express it and talk about.
70 </I>><i> <idea
>
71 </I>><i> Imagine that we have a network with
72 </I>><i> 20 servers and the services. Imagine that it's late night and no oper is
73 </I>><i> available, servers are spliting, and many times due to misconfigured
74 </I>><i> ircd.conf files, autoconnects are not present. So the network will stay
75 </I>><i> splited, until one oper will come and realise that half of the network is
76 </I>><i> not connected. So .. What about puting some
"intelligence
" into the
77 </I>><i> services. For example, (we have the fact that services can somehow know
78 </I>><i> the best connect between
2 servers and an alternative, this could be done
79 </I>><i> easy even providing this information from a db once to the services,
80 </I>><i> server) an /operserv checklinks
05:
00-
08:
00 command, or however you want
81 </I>><i> to call it, will perform a
"clever
" connect at one server that will split.
82 </I>><i> By the mean clever connect, it could be a connect not immediate, so if the
83 </I>><i> server splits now, services will not try to remotelly connect the servers
84 </I>><i> now, they could wait for about
3-
5 minutes, if autoconnets are present the
85 </I>><i> connection will be performed between that time, so no rush to initiate
86 </I>><i> another connect. If now auto connect is not present , and
5 minutes have
87 </I>><i> passed OperServ could initiate a connect. If the connection is achieved,
88 </I>><i> good, nothing to worry from then on, if not, wait
10 minutes now, maybe
89 </I>><i> there is a network problem and try again, if again a failure, incremet a
90 </I>><i> bit the wait time, and try later.
91 </I>><i> </idea
>
93 </I>><i> Sorry for the long post, comments, ideas are welcome.
96 </I>><i> Nick Krassas
97 </I>><i> Dinos @ irc.gr
98 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircadmin at darkness.irc.gr
</A>
101 </I>><i> -----------------------------------------------------------
102 </I>><i> To unsubscribe, mail
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices-request at ircservices.za.net
</A>
103 </I>><i> with the word UNSUBSCRIBE in the subject of the mail.
104 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">http://www.ircservices.za.net/mailman/listinfo/ircservices
</A>
107 Yusuf Iskenderoglu *** eMail
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at rz.uni-karlsruhe.de
</A>
117 <LI>Previous message:
<A HREF=
"001605.html">[IRCServices] Ideas , features
119 <LI>Next message:
<A HREF=
"001600.html">[IRCServices] Nick Identification bug?
121 <LI> <B>Messages sorted by:
</B>
122 <a href=
"date.html#1607">[ date ]
</a>
123 <a href=
"thread.html#1607">[ thread ]
</a>
124 <a href=
"subject.html#1607">[ subject ]
</a>
125 <a href=
"author.html#1607">[ author ]
</a>
projects / irc.git / blob