I've read the section relevant to porting a CGI script over to mod_perl. I didn't understand much of it. Is there anyone who can tell me in simple terms how to make a script execute under mod_perl with the same simplicity that it does under cgi?
During my first test run I discovered that you can't just print off your own HTTP header, but that you have to configure http.conf with "PerlSendHeader On". I did that and it worked on test run two.
But then I had the problem of variables holding the wrong value after successive reloads which in this particular application cause the page to send a passkey which is then deemed to be incorrect and you are logged out. Is it a general rule, or is there any general rule, that you should convert all "my" declarations to "local our"? Will killing all variable values at the end of the script help? What's the best way to do that if so?
I use library files in the application I'm trying to speed up. Not because I learned Perl 4, but because I'm an old Pascal programmer, and that style is comfortable with me. If I use mod_perl, do I have to trash the .lib files and put them all on the same script or convert them all to modules, or is there a way to preserve my programming heritage and let this old dog keep his old fashioned ways?
Thanks for any answers to the above, Jim
_______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
