I'm looking at the information in mod_perl 2 User's Guide (and online) about using VirtualHost and +Parent, with an ithreads-enabled Perl, in order to be able to modify @inc by virtualserver. On my system I basically have that setup, and have tried it, and it seems to work fine (I tried it with prefork, though that appears not to matter except for the inefficiency of course).
I'm wondering what would happen if I -didn't-have an ithreads-enabled Perl, but still set up the httpd.conf with the virtual-host/+parent stanzas? Will it fail on startup with an error about +parent being unsupported or some other error? Or does it run fine but I end up with a shared @inc across all virtual servers perhaps? .............. I have a somewhat limited customer set and each customer will probably run a test & production setup, with mostly the same code in each environment (thus @inc conflicts). I'm wondering what, if anything, they might see.... I take it the only real way around the above situation is either to use an ithreads-enabled Perl or to run separate apaches... is there some other way? Thanks! Dylan
