But if a service want to know who is delayed or not, and if it is +d, it can't.
On Thu, 27 Oct 2005 18:04:29 +0200 Carlo Wood <[EMAIL PROTECTED]> wrote: > On Thu, Oct 27, 2005 at 04:16:52PM +0200, Progs wrote: > > If I have two servers, AA and AB, with AAAAA and ABAAA on #foo, a +D > > channel. > > AAAAA is delayed on #foo and ABAAA is +d. > > There is no such thing as being 'delayed'. > In order to know where to send messages, the JOIN is propagated > to all servers (and services) regardless of the +D. > It's only that the clients don't get to see the JOIN (yet). > So, what you mean is that AAAAA only joined so far and didn't > do anything else yet. > > > There are only AAAAA and ABAAA in #foo. > > When AAAAA speaks on #foo, ABAAA is +d so AB doesn't receive message, > > which is why +d must be propagated thus. > > > so ABAAA doesn't see AAAAA's join. > > Correct. > > > Bug or feature ?:) > > For a service like X/W (what +d was invented for) it makes no difference: > the JOIN is always sent to the service and all servers. > > For a bot that wants to limit it's own bandwidth by using +d, it makes a > difference if it's alone on a server or not I guess. +D is meant for VERY > large > happening/channels however... it seems impractical to assume that there > is such a bot alone on a server in that case. I see no reason to worry > about this. > > -- > Carlo Wood <[EMAIL PROTECTED]> > _______________________________________________ > Coder-com mailing list > Coder-com@undernet.org > http://undernet.sbg.org/mailman/listinfo/coder-com > _______________________________________________ Coder-com mailing list Coder-com@undernet.org http://undernet.sbg.org/mailman/listinfo/coder-com
