Alternatively, look at PerlOptions +Parent which was added for this purpose. From the docs:
+Parent: Create a new parent Perl interpreter for the given VirtualHost and give it its own interpreter pool (implies the Clone option).A common problem with mod_perl 1.0 was the shared namespace between all code within the process. Consider two developers using the same server and each wants to run a different version of a module with the same name. This example will create two parent Perl interpreters, one for each <VirtualHost>, each with its own namespace and pointing to a different paths in @INC...
Clint
In reply to Re: Writing mod_perl in multi-developer environment
by clinton
in thread Writing mod_perl in multi-developer environment
by SheridanCat
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |