On Thursday, February 20, 2003, at 10:51 PM, Stas Bekman wrote:
Why not? Use a separate module to drive the others?
package My::PostConfig;
BEGIN {
# whatever needs to be done for other modules
}
1;
startup.pl:
---
use My::PostConfig
Excellent point, and a quick experiment on my end
Hi All,
I'm writing a module that will run in Apache and has important code
that needs to run after all modules have loaded but before Apache forks
and starts serving requests. Since mod_perl 1.x ignores CHECK and INIT
blocks, and BEGIN blocks run too early for what I'm doing, I was
wondering
David Wheeler wrote:
Hi All,
I'm writing a module that will run in Apache and has important code that
needs to run after all modules have loaded but before Apache forks and
starts serving requests. Since mod_perl 1.x ignores CHECK and INIT
blocks, and BEGIN blocks run too early for what I'm
On Thursday, February 20, 2003, at 07:04 PM, Stas Bekman wrote:
PerlChildInitHandler? e.g. used by Apache::DBI to pre-connect to the
db.
Yeah, but I was looking for something pre-fork. Anything come to mind?
Thanks,
David
--
David Wheeler AIM: dwTheory
David Wheeler wrote:
On Thursday, February 20, 2003, at 07:04 PM, Stas Bekman wrote:
PerlChildInitHandler? e.g. used by Apache::DBI to pre-connect to the db.
Yeah, but I was looking for something pre-fork. Anything come to mind?
startup.pl?
in 2.0 you have: PerlPostConfigHandler
On Thursday, February 20, 2003, at 09:41 PM, Stas Bekman wrote:
startup.pl?
Won't work too well in a module, I think. I have a workaround for my
problem for now, but it ain't pretty.
in 2.0 you have: PerlPostConfigHandler
http://perl.apache.org/docs/2.0/user/handlers/
David Wheeler wrote:
On Thursday, February 20, 2003, at 09:41 PM, Stas Bekman wrote:
startup.pl?
Won't work too well in a module, I think. I have a workaround for my
problem for now, but it ain't pretty.
Why not? Use a separate module to drive the others?
package My::PostConfig;
BEGIN
