On 19 Dec 2005, at 14:33, Stas Bekman wrote:
JT Smith wrote:
Yup, I've actually already done it that way with both
Parallel::ForkManager in one instance and Proc::Queue as an
alternative. I added in event handling with both Event and Event::Lib
as seperate trials. All those implementations were relatively easy to
do. But the question becomes, why? If everything else is running in
Apache, why start a seperate service to run these tasks? And again, I
said I want to go crazy. Let's not figure out how else we could do
that (I already know that), but how could we do it using Apache?
Here at mailchannels.com we have first used mp2 to handle the email
traffic shaping entirely inside mod_perl2, but the nature of our
product is so different from serving HTTP, it just won't scale (mostly
memory-wise, but also too many processes).
Not sure what you mean by it not scaling - can you elaborate? Sure it
uses more ram than multiplexing, but even for a high traffic mail
server like apache.org's the mail-in-apache2 model works well
(apache.org uses Apache::Qpsmtpd for email).
I'm curious as to how you've mixed things up though - if the details
aren't private IP I'd love to know more.
Matt.
