thanks for letting me know this.
James Smith wrote:
mpm_event like all Apache mpm_s is much better at handling "issues" where nginx
just goes F* and returns nothing. When we have issues we can detect them on apache mpms -
but we often fail to see nginx errors as it sort of just dies!
as it sort of just dies!
-Original Message-
From: pengyh
Sent: 09 August 2022 13:04
To: James Smith ; modperl@perl.apache.org
Subject: Re: is mpm_event safe for modperl handler? [EXT]
I think running Ignix as front-end server and mod_perl for backend server is
the more popular choice.
I think running Ignix as front-end server and mod_perl for backend
server is the more popular choice.
If you want the speed of mod_event for static content and the power of mod_perl
for dynamic content - the best way is to run a lightweight mod_event apache in
front of a mod_prefork to run
f like SSL etc
is handled on the mod_event instance keeping the mod_worker instance clean..
It also allows you to run two apaches on a single box - a "test" and a "live"
-Original Message-
From: pengyh
Sent: 05 August 2022 02:21
To: modperl@perl.apache.org
Subject: Re:
thanks. that does sound sorry.
No and neither is mod_worker. The only mpm you can safely use is
prefork. This is, in my opinion, mod_perl's fatal flaw which will doom it.
No and neither is mod_worker. The only mpm you can safely use is prefork.
This is, in my opinion, mod_perl's fatal flaw which will doom it.
On Thu, Aug 4, 2022 at 2:27 AM pengyh wrote:
> Hello
>
> yes i know mpm_prefork is pretty good for modperl applications.
> if I run modperl handler (for
Hello
yes i know mpm_prefork is pretty good for modperl applications.
if I run modperl handler (for example, PerlAccessHandler) under
mpm_event, is it safe for a production environment?
thanks.
