Stas Bekman wrote:
Here is a bizarre thing I've noticed. when running:
% env MOD_PERL_TRACE=h t/TEST -start
modperl_handler_resolve: [5465/1078234656 rabbit.stason.org:8529] handler Apache::PerlSections was not compiled at startup, attempting to resolve using server conf pool 0x81420a8
modperl_handler_resolve: [5465/1078234656 rabbit.stason.org:8529] handler Apache::PerlSections was not compiled at startup, attempting to resolve using server conf pool 0x81420a8
prints about 8 times. any idea why? Each time it then reports that it resolved that handler, but then it does the same cycle again...
I've traced it down to this line :
handler = modperl_handler_new(p, handler_name);
So basically, to be able to use the existing modperl_handler_* framework to run <perl> sections, I am creating a brand new handler for each section, creating that behaviour.
But can you arrange for it not to think that it wasn't resolved yet, keeping things as they are?
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
