[IRCServices] Scalability

[Andrew Church]

>In my opinion the problem that is being ignored is the ability of services 
>to act concurrently on data.

     This isn't a "problem" if you had no intention of doing it in the
first place.  I don't know what Andrew Kempe's plans are, of course, but
I never intended Services to work on every network around; I figured from
the start that Services would probably not work on a network the size of
(e.g.) DALnet, and that was fine with me; that would take a different sort
of program design, which wouldn't be as fit for the 20-30 user network I
was designing Services for.  That said, I see no reason not to
incorporate changes which improve performance on larger networks if they
have no real disadvantages.

>Pick one and go with it :)  There's no use adding a bunch of bells and 
>whistles [...] if the end result is the same thing you started with --
>only with code that is harder to understand and update.

     Have you tried looking at the current database load/save code?
That's one of the uglier pieces of code I've written, and that's even
after the cleanup I put in around version 4.0.  Rewriting it would be
an improvement in and of itself, no matter what method was used.

  --Andrew Church
    achurch at dragonfire.net
    http://achurch.dragonfire.net/

---------------------------------------------------------------
To unsubscribe, send email to majordomo at ender.shadowfire.org
with "unsubscribe ircservices" in the body, without the quotes.