+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<HTML>
- <HEAD>
- <TITLE> [IRCServices] Scalability
- </TITLE>
- <LINK REL="Index" HREF="index.html" >
- <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Scalability&In-Reply-To=007801c03419%243a23def0%249c011ac4%40shadow">
- <META NAME="robots" CONTENT="index,nofollow">
- <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <LINK REL="Previous" HREF="000851.html">
- <LINK REL="Next" HREF="000855.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[IRCServices] Scalability</H1>
- <B>Scott Seufert</B>
- <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Scalability&In-Reply-To=007801c03419%243a23def0%249c011ac4%40shadow"
- TITLE="[IRCServices] Scalability">anarki at flamebait.org
- </A><BR>
- <I>Thu Oct 12 04:34:23 PDT 2000</I>
- <P><UL>
- <LI>Previous message: <A HREF="000851.html">[IRCServices] Scalability
-</A></li>
- <LI>Next message: <A HREF="000855.html">[IRCServices] Ircd's and Services....
-</A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#852">[ date ]</a>
- <a href="thread.html#852">[ thread ]</a>
- <a href="subject.html#852">[ subject ]</a>
- <a href="author.html#852">[ author ]</a>
- </LI>
- </UL>
- <HR>
-<!--beginarticle-->
-<PRE>At 08:54 AM 10/12/2000 +0200, you wrote:
-
-><i> > >In my opinion the problem that is being ignored is the ability of
-</I>><i>services
-</I>><i> > >to act concurrently on data.
-</I>><i> >
-</I>><i> > This isn't a "problem" if you had no intention of doing it in the
-</I>><i> > first place. I don't know what Andrew Kempe's plans are, of course, but
-</I>><i> > I never intended Services to work on every network around; I figured from
-</I>><i> > the start that Services would probably not work on a network the size of
-</I>><i> > (e.g.) DALnet, and that was fine with me; that would take a different sort
-</I>><i> > of program design, which wouldn't be as fit for the 20-30 user network I
-</I>><i> > was designing Services for. That said, I see no reason not to
-</I>><i> > incorporate changes which improve performance on larger networks if they
-</I>><i> > have no real disadvantages.
-</I>><i>
-</I>><i>I agree with this. Currently IRC Services is mostly used by networks with
-</I>><i>less than 500 users. There are a number that are less than 2000 and only a
-</I>><i>few with more than that. My aim is to keep the majority happy while still
-</I>><i>trying to allow the huge networks to function.
-</I>
-<snip>
-
-Actually I would think that by the time a network reaches 2k users, there
-would a good chance that there would be someone in the staff that would
-know how to code services to upgrade/re-code as needed. I agree with the
-current approach of pleasing as many people as possible, but as we all
-know, a line is to be drawn somewhere.
-
-I would only hope that under IRCServices current license, such coders would
-release their code in due time.
-
-Scott Seufert
-aka katsklaw
-Server Admin
-Excalibre.ShadowFire.Org
-
-
----------------------------------------------------------------
-To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
-with "unsubscribe ircservices" in the body, without the quotes.
-
-
-</PRE>
-
-<!--endarticle-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="000851.html">[IRCServices] Scalability
-</A></li>
- <LI>Next message: <A HREF="000855.html">[IRCServices] Ircd's and Services....
-</A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#852">[ date ]</a>
- <a href="thread.html#852">[ thread ]</a>
- <a href="subject.html#852">[ subject ]</a>
- <a href="author.html#852">[ author ]</a>
- </LI>
- </UL>
-
-</body></html>
projects / irc.git / blobdiff