Re^2: different versions of same Perl module in different Apache vhosts

Would I need to use it in both vhost definitions? Could I just leave the primary alone and put the development module in some other dir and use Apache::PerlVINC with the development vhost definition? I can live with degraded performance on just the development site.

Comment on Re^2: different versions of same Perl module in different Apache vhosts

Replies are listed 'Best First'.
Re^3: different versions of same Perl module in different Apache vhosts by perrin (Chancellor) on Jun 07, 2004 at 02:33 UTC
I'm not sure about this, since I've never used Apache::PerlVINC. It seems like it should work, but would probably still affect performance in both. I think Apache::PerlVINC causes the modules to be re-compiled every time, which is a performance hit, and will ruin the copy-on-write shared memory that mod_perl would otherwise benefit from.	[reply]