[IRCServices] Ideas , features

[Yusuf Iskenderoglu]

Hello ;

I do not see, why this idea has to be denied right from the beginning.
I personally see this useful, because:


- The current implementation might be expanded, to include the map of the
network, in a way that services manages a structure for each server, to
see who is linked to whom, etc.

- This can be used to implement Bahamut's NOQUIT, because, that way,
services WILL know, which nicknames have quit due to a split, without
needing to see the quit message from the hub it is connected.

- This can be / is being used to implement the StatServ's MAP command
extremely easily.

- This can also be used in a timer event, as described, to maintain the
linkage. The reality, that the linking had to occur automatically, is of
course wanted, but never realised effectively. I can tell from own
experience, where our hub is not configured to send a connect itself, but
is designed to wait for connects. This way, the server is not keeping
track of who was disconnected, or whether it should connect, etc.
If services itself sent the connect command, because it saw the squit, it
would of course be managed quicker. I do not see, why some of us are
declaring this as a non-capable administration.

Regards,
yusuf

 On Wed, 14 Mar 2001 dreamer at darkness.gr
wrote:

> Greetings all,
> 	I had an idea long time ago, i think that the list is appropriate
> to express it and talk about.
> <idea>
> Imagine that we have a network with
> 20 servers and the services. Imagine that it's late night and no oper is
> available, servers are spliting, and many times due to misconfigured
> ircd.conf files, autoconnects are not present. So the network will stay
> splited, until one oper will come and realise that half of the network is
> not connected. So .. What about puting some "intelligence" into the
> services. For example, (we have the fact that services can somehow know
> the best connect between 2 servers and an alternative, this could be done
> easy even providing this information from a db once to the services,
> server) an /operserv checklinks 05:00-08:00 command, or however you want
> to call it, will perform a "clever" connect at one server that will split.
> By the mean clever connect, it could be a connect not immediate, so if the
> server splits now, services will not try to remotelly connect the servers
> now, they could wait for about 3-5 minutes, if autoconnets are present the
> connection will be performed between that time, so no rush to initiate
> another connect. If now auto connect is not present , and 5 minutes have
> passed OperServ could initiate a connect. If the connection is achieved,
> good, nothing to worry from then on, if not, wait 10 minutes now, maybe
> there is a network problem and try again, if again a failure, incremet a
> bit the wait time, and try later.
> </idea>
>
> Sorry for the long post, comments, ideas are welcome.
>
> Regards,
> Nick Krassas
> Dinos @ irc.gr
> ircadmin at darkness.irc.gr
>
>
> -----------------------------------------------------------
> To unsubscribe, mail ircservices-request at ircservices.za.net
> with the word UNSUBSCRIBE in the subject of the mail.
> http://www.ircservices.za.net/mailman/listinfo/ircservices
>

Yusuf Iskenderoglu  ***  eMail uhc0 at rz.uni-karlsruhe.de