At 10:07 AM 9/13/00 -0400, Bennett Todd wrote:
>2000-09-13-03:29:16 Hildo Biersma:
> > Some would argue that a better design is required. Apache 2.0 will
> > use a mixed thread/process model, and mod_perl 2.0 will run
> > selected threads within one process, precisely to alleviate these
> > problems. So it's not necessarily perl's fault...
>
>Some would argue whether that constitutes a better design. Some
>would even claim that threads are usually a wart with additional
>complexity and fragility bolted onto an existing bloater of a bad
>design, to attempt to make it faster, invariably at the expense of
>stability.
Some would argue the moon is made of green cheese, the earth is flat, and
the Apollo landings were filmed in a studio in Arizona, too. I think you'll
find threads are useful in a rather large number of places. (The set of
which does not necessarily map to the set of places they are used, but
that's a problem of mis-application of tools, not threads)
>If more speed is needed, make the part that's currently too slow
>_simpler_, not _more_complex_.
I think you'll find it rather more useful to make the part that's currently
too slow *faster*, rather than more or less complex.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk