>If I were you I wouldn't do that. >If I were you I wouldn't do that either.
I know my limitations, and I'm sure you know that of mod_perl's. At this point, I have to lean toward "code" and not "I ran out of time". Maintaining two codebases (running under vanilla CGI is a requirement, not a feature) is just impossible in my current timeframe.
>> I'm seeing two separate issues > >Code handlers, get rid of globals and closures, run 'httpd -X'.
Could you tell me more what you mean by "code handlers"?
If I "undef" certain things at the end of scripts (like undef $settings, undef $final_template, undef $data), would that help? Are those three variables considered globals to mod_perl (they're lexical to index.cgi::main)? my() to our() didn't help.
As for -X, wouldn't that merely confirm children caching? What would I learn from confirming or denying the behavior under -X?
Thanks for the reply.
-- Morbus Iff ( i put the demon back in codemonkey ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ Spidering Hacks: http://amazon.com/exec/obidos/ASIN/0596005776/disobeycom icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
