in reply to mod_perl with Apache::Registry with CGI.pm design considerations
I have been researching mod_perl and how to migrate my older perl scripts to it. What I have found are a couple of things:
- Always use strict; and turn on warnings -- This will show you if a var will fall out of scope
- Always pass any variables to a sub -- This will make sure none of them become global.
- Creating a .pm file with your functions will allow Apache to handle them better.
- Instead of use CGI; do a require CGI; -- This is supposed to destroy any "Global" variables created or use by CGI
- Turn off KeepAlive -- (Unless you need it like me :(
- Apache::DBI is great!
- Comment on Re: mod_perl with Apache::Registry with CGI.pm design considerations
--BigJoe
Learn patience, you must.
Young PerlMonk, craves Not these things.
Use the source Luke.
Replies are listed 'Best First'. | |
---|---|
Re: Re: mod_perl with Apache::Registry with CGI.pm design considerations
by hacker (Priest) on Jun 14, 2002 at 14:03 UTC | |
by Anonymous Monk on Nov 13, 2002 at 14:11 UTC | |
Re: Re: mod_perl with Apache::Registry with CGI.pm design considerations
by perrin (Chancellor) on Jun 14, 2002 at 14:32 UTC |
In Section
Seekers of Perl Wisdom