Re^3: Scope of @INC in mod

Maybe, but not within one persistent Perl-interpreter as mod_perl does.

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

Comment on Re^3: Scope of @INC in mod_perl 2

Replies are listed 'Best First'.
Re^4: Scope of @INC in mod_perl 2 by WizardOfUz (Friar) on Nov 04, 2009 at 17:52 UTC
`PerlOptions +Parent` gives you a completely new Perl interpreters pool for each VirtualHost. Please take a look at the mod_perl documentation.	[reply] [d/l]
Re^5: Scope of @INC in mod_perl 2 by CountZero (Bishop) on Nov 04, 2009 at 18:55 UTC
Of course, and thanks for reminding me. However, if you do that too much you will quickly run out of memory. The nice thing about a well installed and configured mod_perl is that you can benefit of the shared memory and I have a gut-feeling that the problem of the OP can be solved by configuring each virtual host rather than by hard-coding the differences inside a module. 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	[reply]