| I meant a different startup per virtual host, not per child process. It's perfectly ok to specify a PerlRequire for each virtual host or even in .htaccess, but I think that's a dirty habbit to get into. As the complete perl namespace is shared between all your virtual hosts there is really no benifit, just drawbacks: modules required before Apache forks off will result in all childs using a single copy of that module, but required modules after that will load a copy for each child process. Ime
- perl initialization per virtual host... is it possible William Deegan
- Re: perl initialization per virtual host... is it po... William Deegan
- Re: perl initialization per virtual host... is i... Ime Smits
- Re: perl initialization per virtual host... ... William Deegan
- Re: perl initialization per virtual host... Doug MacEachern
- Re: perl initialization per virtual host... is i... David Hodgkinson