[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices-coding / 2004 / 003009.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices Coding] Feature request: No logonnews after netsplit
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Feature%20request%3A%20No%20logonnews%20after%20netsplit&In-Reply-To=">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="003006.html">
   <LINK REL="Next"  HREF="003010.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices Coding] Feature request: No logonnews after netsplit</H1>
    <B>Wolfgang Urban</B> 
    <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Feature%20request%3A%20No%20logonnews%20after%20netsplit&In-Reply-To="
       TITLE="[IRCServices Coding] Feature request: No logonnews after netsplit">ircservices-coding at tou.de
       </A><BR>
    <I>Sat Apr 10 07:15:05 PDT 2004</I>
    <P><UL>
        <LI>Previous message: <A HREF="003006.html">[IRCServices Coding] Bug using svs4-db in
	svs5(autodeop/nojoin-level)
</A></li>
        <LI>Next message: <A HREF="003010.html">[IRCServices Coding] Feature request: No logonnews after netsplit
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#3009">[ date ]</a>
              <a href="thread.html#3009">[ thread ]</a>
              <a href="subject.html#3009">[ subject ]</a>
              <a href="author.html#3009">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Hi all,

i think it would be very useful if services could detect when a netmerge (of
any server on its own net, at any time) is completed. This would bring the
following advantages/features:

1.) If you know that a server is linking at the moment and merging its data
with the net by sending its users, channels, etc., you would also be able to
determine whether a new user (from services' point of view) is just being
introduced as part of the netmerge and was still on his server or logged
onto his server shortly ago.
Currently services send their logonnews to every &quot;new&quot; user they see on the
net, even if this user has already received them during his irc session.

2.) Services would be able to wait until a linking server has completed its
netmerge and then set chanmodes like autoop/voice - but only if necessary.

All in all it would reduce the services traffic and the annoyance level for
the users in case of a netsplit or svs restart.

I think there is an easy way to determine the end of an netmerge without
help of any special ircd features:
You just need to send a PING to any new server on the net. If we can assume
that every ircd software first sends all its own nicks/chans/.. and then
starts to reply to commands, you should get the PONG after receiving all
netmerge specific data. Before this PONG is being received, logonnews
shouldn't be sent to users on this server and they also shouldn't get autoop
or autovoice. When we get the PONG, we need to recheck the
autoop/autovoice-status of every user on the server that just linked.

Wolle


</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="003006.html">[IRCServices Coding] Bug using svs4-db in
	svs5(autodeop/nojoin-level)
</A></li>
	<LI>Next message: <A HREF="003010.html">[IRCServices Coding] Feature request: No logonnews after netsplit
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#3009">[ date ]</a>
              <a href="thread.html#3009">[ thread ]</a>
              <a href="subject.html#3009">[ subject ]</a>
              <a href="author.html#3009">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices Coding] Feature request: No logonnews after netsplit
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Feature%20request%3A%20No%20logonnews%20after%20netsplit&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="003006.html">
	11	<LINK REL="Next" HREF="003010.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices Coding] Feature request: No logonnews after netsplit</H1>
	15	<B>Wolfgang Urban</B>
	16	<A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Feature%20request%3A%20No%20logonnews%20after%20netsplit&In-Reply-To="
	17	TITLE="[IRCServices Coding] Feature request: No logonnews after netsplit">ircservices-coding at tou.de
	18	</A><BR>
	19	<I>Sat Apr 10 07:15:05 PDT 2004</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="003006.html">[IRCServices Coding] Bug using svs4-db in
	22	svs5(autodeop/nojoin-level)
	23	</A></li>
	24	<LI>Next message: <A HREF="003010.html">[IRCServices Coding] Feature request: No logonnews after netsplit
	25	</A></li>
	26	<LI> <B>Messages sorted by:</B>
	27	<a href="date.html#3009">[ date ]</a>
	28	<a href="thread.html#3009">[ thread ]</a>
	29	<a href="subject.html#3009">[ subject ]</a>
	30	<a href="author.html#3009">[ author ]</a>
	31	</LI>
	32	</UL>
	33	<HR>
	34	<!--beginarticle-->
	35	<PRE>Hi all,
	36
	37	i think it would be very useful if services could detect when a netmerge (of
	38	any server on its own net, at any time) is completed. This would bring the
	39	following advantages/features:
	40
	41	1.) If you know that a server is linking at the moment and merging its data
	42	with the net by sending its users, channels, etc., you would also be able to
	43	determine whether a new user (from services' point of view) is just being
	44	introduced as part of the netmerge and was still on his server or logged
	45	onto his server shortly ago.
	46	Currently services send their logonnews to every "new" user they see on the
	47	net, even if this user has already received them during his irc session.
	48
	49	2.) Services would be able to wait until a linking server has completed its
	50	netmerge and then set chanmodes like autoop/voice - but only if necessary.
	51
	52	All in all it would reduce the services traffic and the annoyance level for
	53	the users in case of a netsplit or svs restart.
	54
	55	I think there is an easy way to determine the end of an netmerge without
	56	help of any special ircd features:
	57	You just need to send a PING to any new server on the net. If we can assume
	58	that every ircd software first sends all its own nicks/chans/.. and then
	59	starts to reply to commands, you should get the PONG after receiving all
	60	netmerge specific data. Before this PONG is being received, logonnews
	61	shouldn't be sent to users on this server and they also shouldn't get autoop
	62	or autovoice. When we get the PONG, we need to recheck the
	63	autoop/autovoice-status of every user on the server that just linked.
	64
65	Wolle
66
67
68
69	</PRE>
70
71	<!--endarticle-->
72	<HR>
73	<P><UL>
74	<!--threads-->
75	<LI>Previous message: <A HREF="003006.html">[IRCServices Coding] Bug using svs4-db in
76	svs5(autodeop/nojoin-level)
77	</A></li>
78	<LI>Next message: <A HREF="003010.html">[IRCServices Coding] Feature request: No logonnews after netsplit
79	</A></li>
80	<LI> <B>Messages sorted by:</B>
81	<a href="date.html#3009">[ date ]</a>
82	<a href="thread.html#3009">[ thread ]</a>
83	<a href="subject.html#3009">[ subject ]</a>
84	<a href="author.html#3009">[ author ]</a>
85	</LI>
86	</UL>
87
88	</body></html>