You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Uri Bernstein <ur...@gurunet.com> on 2000/05/11 17:08:07 UTC
Virtual servers mixing up "require"d scripts
Hi,
At my company we're developing a project using mod_perl and
Apache::Registry. The project consists of one main script, which
"require"s a couple of other scripts and calls functions contained in
them. In order to provide a "private" development environment to each of
our developers, we defined a virtual server per developer. Each virtual
server has its root aliased to a different directory, which contains one
developr's "private" versions of the scripts.
This seems to work fine most of the time, but, sometimes, the "require"d
scripts get mixed up: The "main" script from one virtual server seems to
be using "require"d scripts belonging to another virtual server.
We're using Apache 1.3.4 / mod_perl 1.18 / perl 5.004_04 (Yes, they're
oldies, I know).
Any help would be much appreciated.
--
Uri Bernstein
Re: Virtual servers mixing up "require"d scripts
Posted by Ged Haywood <ge...@jubileegroup.co.uk>.
Hi there,
On Thu, 11 May 2000, Uri Bernstein wrote:
> Hi,
> In order to provide a "private" development environment to each of
> our developers, we defined a virtual server per developer. Each virtual
> server has its root aliased to a different directory
> [snip]
> This seems to work fine most of the time, but, sometimes, the "require"d
> scripts get mixed up: The "main" script from one virtual server seems to
> be using "require"d scripts belonging to another virtual server.
You shold use one real server per developer. Make them listen on
different ports (>1024). You won't lose much on memory.
Yeah, it's a pain. And I'd upgrade to 1.3.12/1.23/5.005_03.
73,
Ged.