Re: mod_perl2 confusion

Thank you for your early responses.

I just found out something here: http://perl.apache.org/docs/2.0/rename.html

It says that the Mod_perl2 API underwent a last minute API change before the official release. It goes on to say:

"Constants under the Apache::* namespace, such as Apache::OK, are now called as Apache2::Const::* (for example, Apache2::Const::OK)."

And most of the Modules which were under the "Apache::" name are now "Apache2::" In this 1.99x version, I found one Apache::Const module so probably that explains it.

But because it has been suggested here(in the above comments) not to use this version (1.99x), I have to reconsider using it.

Please add in your valuable suggestions, if any. Thanks.

Comment on Re: mod_perl2 confusion

Replies are listed 'Best First'.
Re^2: mod_perl2 confusion by randyk (Parson) on Sep 20, 2005 at 13:33 UTC
You should definitely upgrade to the most recent version; as has already been mentioned, Win32 ppm packages exist that can be used to do this. Before doing so, it would be a good idea to remove the old installation, including the mod_perl.so Apache module in the Apache2 modules subdirectory. If mod_perl is registered with your ppm utility, you can remove it from within the ppm shell; otherwise, see the discussion of the mod_perl 2 renaming to see which files need to be manually removed - unless you have some custom Apache modules, a good start to this would be to just remove Apache2.pm and mod_perl.pm in C:\Perl\site\lib, and also the Apache subdirectories under C:\Perl\site\lib and C:\Perl\site\lib\auto.	[reply]
Re^2: mod_perl2 confusion by ides (Deacon) on Sep 20, 2005 at 13:28 UTC
My suggestion would be to stay away from mod_perl 1.99.x at all costs. It's no longer maintained. There are bugs, not to mention the API changes. You'll run into issues trying to use other mod_perl related CPAN modules that only work with 2.0.x. Also, if you run into any problems and ask for help 99% of the time everyone is going to tell you to upgrade to 2.0.x to see if that fixes your problem. Frank Wiles <frank@wiles.org> http://www.wiles.org	[reply]