Geoffrey Young wrote:
> > -----Original Message-----
> > From: Ged Haywood [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 11, 2000 12:26 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Virtual servers mixing up "require"d scripts
> >
> >
> > 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.
>
> as an alternative, I think this crept into the latest guide:
>
> http://perl.apache.org/guide/control.html#Starting_a_Personal_Server_for_E
>
> HTH
>
> --Geoff
Thanx, Geoff and Ged, for your help. I guess I'll go with a multiple-ports
solution (although having people's names as a their virtual host names was
really convenient). However, just out of curiosity, I wonder if someone can
give me some insight into this problem:
- Is this a known bug, or an unavoidable by-product of the way mod_perl works?
- Is it related to the fact I'm using Apache::Registry? Would switching to the
native Apache API fix it?
- Is it related to the fact I'm using "require", with ".pl" files? Would
switching to "use" (with .pm modules) fix it?
--
Uri
