Hello! after being a long time away (over 4 years since my last post on this list), I started again with some development with mod_perl for this company that I currently work for.
I'm having some trouble with CGI.pm working with mod_perl2. I searched the mailing-list for this and I found many different point of views for this problem, some say it should work, and some say it doesn't. I've tested it and it really doesn't work "as is". This guy clearly says that CGI.pm is incompatible with mod_perl2: http://marc.theaimsgroup.com/?l=apache-modperl&m=103619647305553&w=2 This isn't really a big problem, but I have 3 ways out: 1) help make CGI.pm compatible with mod_perl2 if at all possible 2) replace all CGI.pm calls with simple homemade cgi functions (not difficult, it's just that we have to correct many scripts that already count on CGI.pm), or use that "Apache::compat" thing 3) downgrade apache to 1.3.27 and mod_perl to 1.27 and be happy Option 3 seems okay, excect for the fact that I am that kind of Linux user that is always upgrading everything to the latest version possible. This applies to linux kernel, apache, etc. I don't really have a reason to do this, but I have always done it anyway. So to use apache 1.3.27 and mod_perl 1.27 goes against my nature. Am I going to hell if I do this? Seriously, does mod_perl2 offer much more features and benefits then mod_perl1? I really only care for speed and stability for simple perl scripts that use CGI/DBI/DBD::mysql modules. Is it okay if I use mod_perl and apache 1.x today, or it's better to move to 2.x already? Thanks, Henrique.
