> 1- Currently I have designated a /pm directory to contain my mod_perl > codes, a collection of classes. I then have instances of these launched > from non /pm directory. I did this so that I don't have to be back at > cgi-bin perdicament where all my CGIs are in one directory. I never > liked that style. But I'm still forced to put my base classes in /pm. > > Is there a way to instruct HTTP that perl code in any directory should > be used as mod_perl similar to ExecCGI. Or perhaps for a better/cleaner > approach, any perl code with some extension such as foo.cgi-mp or foo.cmp > (Cgi-Mod-Perl).
Look at the <FilesMatch> directive in the Apache documentation. You might also want Apache::Dispatch. > 2- I currently have to restart my HTTP for changes to my mod_perl code > take affect. Is there any way so I don't have to do this. Apache::StatINC or Apache::Reload. - Perrin
