Hi all,
DHZ> use lib /path1/lib.pm
DHZ> ..
DHZ> and in the startup file of vhost 2
DHZ> ..
DHZ> use lib /path2/lib.pm
DHZ> ..
DHZ> This works for me.
DHZ> Both lib.pm's are separated because new perl interpreters are used
for DHZ> vhost1 and vhost2.
Thanks Helmut, I will try this solution (PerlOp
DHZ> use lib /path1/lib.pm
DHZ> ..
DHZ> and in the startup file of vhost 2
DHZ> ..
DHZ> use lib /path2/lib.pm
DHZ> ..
DHZ> This works for me.
DHZ> Both lib.pm's are separated because new perl interpreters are used for
DHZ> vhost1 and vhost2.
Thanks Helmut, I will try this solution (PerlOptions +Pa
Alexander Shipitsyn wrote:
I need to have different code (and same module names!) for production
and development site.
Also I need to have (for example) two different production sites
(production sites for company A and company B) (site-A-production and
site-B-production), developed with same modul
Hi Alexander,
do you have a threaded Perl interpreter?
I also use
..
PerlOptions +Parent
..
but in the vhost-config files (which should make no difference?)
and in the startup files of vhost 1
..
use lib /path1/lib.pm
..
and in the startup file of vhost 2
..
use lib /path2/lib.pm
..
This works
Hi Alexander,
do you have a threaded Perl interpreter?
I also use
..
PerlOptions +Parent
..
but in the vhost-config files (which should make no difference?)
and in the startup files of vhost 1
..
use lib /path1/lib.pm
..
and in the startup file of vhost 2
..
use lib /path2/lib.pm
..
This works
> I known about issue "Why do variables retain their values between
> requests?" in FAQ and I always use my()/local() for not retain values
> of variables between requests.
This applies to asp pages because they are wrapped in a subroutine,
"my" variables then become local to the current request
