|There's more than one way to do things|
mod_perl and Apache::Registry (code)by deprecated (Priest)
|on Nov 14, 2001 at 00:07 UTC||Need Help??|
deprecated has asked for the
wisdom of the Perl Monks concerning the following question:
I'm having a problem with a perl script on an apache server using mod_perl. This is a mostly default mandrake 8.1 install, but I know my way around apache configs.
This is a very _old_ server, and it literally takes 21% of the cpu to launch this cgi. It takes a few (maybe 5) seconds to actually display to the browser. However, it takes less than one second if i rename 'index.cgi' to 'index.pl'. As I understand it, this is mod_perl working for me. Now, a friend told me I could use Apache::Registry to 'cache' the file in the server so that it would not have to re-read it every time (the pod seems to agree with this). So I tossed a use Apache::Registry in there, and let 'er rip.
First, the page displays right the first and only time I load it. then after that, it just spits out the source. If add '.pl' to the "add handler" section of the config file (after .cgi), it seems that mod_perl does not get to process it, and it reverts to being slow.
I do in fact have the
directive in the config file. I suspect that it may have something to do with:
and the caching of browsers and the like. Has anyone seen behaviour like this out of mod_perl? I'm rather new to it.