----- Original Message -----
From: "Ime Smits" <[EMAIL PROTECTED]>
To: "William Deegan" <[EMAIL PROTECTED]>
Cc: "G.W. Haywood" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, September 14, 2000 2:26 PM
Subject: Re: perl initialization per virtual host... is it possible
>
>
> | 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.
When I do that a "SetEnv" in my virtual host doesn't seem to get
passed to the startup.pl...
Is that the expected behavior?
-Bill
