I think you really only want to load a different config file depending on the virtual host being requested. You shouldn't need to do anything fancy with your modules just 'use' then in your scripts/handlers and load the appropriate config file.
If you have some modules which are similarly named but customised for each virtual host, then you will need to look at fixing this by either merging or renaming them and relagating any differences to your config file.
Configuration Files: Writing, Dynamically Updating and Reloading <- a good read
Update:
If anybody has a solution to minimize the amount of memory taken when using the same set of modules from 2 vhosts, I'd be very glad.
Are you running cgi scripts through registry, or mod_perl handlers?
Have you gotten to this in the tuning docs..? Preloading Registry Scripts at Server Startup
cheers,
J
In reply to Re: how mod_perl finds if code has already been compiled
by edoc
in thread how mod_perl finds if code has already been compiled
by Sihal
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |