Python company worth $100M

[Mike Fletcher]

Nope, don't think you're missing anything. If I recall correctly, the
asyncore docs even mention their assumption that the processing to be done
per call is trivial.  Since all other channels are "blocked" while the
compute-heavy call is processing, the system will suffer performance
degradation for all other clients.  Thread-pools seem to be a decent
approach for longer-running calls.

Cheers,
Mike

-----Original Message-----
From: python-list-admin at python.org
[mailto:python-list-admin at python.org]On Behalf Of Aahz Maruch
Sent: November 10, 1999 12:16 PM
To: python-list at python.org
Subject: Re: Python company worth $100M


In article <033201bf2b73$ad1e49e0$f29b12c2 at secret.pythonware.com>,
Fredrik Lundh <fredrik at pythonware.com> wrote:
>
>  [ Searchbutton.com ]
>and if you look at the technical credits page, what do you
>find?
>
>    http://www.searchbutton.com/misc/technicalCredits
>
>asynclib again, of course ;-)

Actually, we're moving away from asyncore in favor of threads.  Unless
we're missing something obvious, asyncore just doesn't do well with
compute-heavy processes.
--
> I wrote:
> > a slightly hairer design issue is what combinations
> > of pattern and string the new 're' will handle.
>

--
http://www.python.org/mailman/listinfo/python-list