If you have custom modules for each virtual server, these modules should be named differently and if the differences are just matters of configuration which are hard-coded into the modules then you should factor out the differences and put it in separate configuration files that are specific for each virtual server.
It is never a good idea to have same-named modules that live in the same namespace do different things (other than through a config-file). That way lies madness and problems.
CountZero
A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
In reply to Re: Scope of @INC in mod_perl 2
by CountZero
in thread Scope of @INC in mod_perl 2
by atemon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |