Re: multiple developers on one Sever

2004-12-22 Thread Perrin Harkins
On Wed, 2004-12-22 at 13:15 +0100, Henning Meyer wrote: > I understand this - but I want to use Apache::Registry for > performance-reasons. How can I get different configurations in different > Versions of my system? > Should I use something like Config::Tiny? > Or can I use Apache::PerlRun just

Re: multiple developers on one Sever

2004-12-22 Thread Tom Schindl
Well you are not stating which mp-version you are running but for: mp1: http://perl.apache.org/docs/1.0/guide/modules.html#Apache__PerlVINC___Allows_Module_Versioning_in_Location_blocks_and_Virtual_Hosts mp2: http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_ Tom Henning Me

Re: multiple developers on one Sever

2004-12-22 Thread Vadim
> I understand this - but I want to use Apache::Registry for > performance-reasons. How can I get different configurations in different > Versions of my system? > Should I use something like Config::Tiny? > Or can I use Apache::PerlRun just for my config.pl - which I include via > require 'config.

Re: multiple developers on one Sever

2004-12-22 Thread Henning Meyer
Arun pandey schrieb: I guess the problem might be with your PerlHandler, coz Apache::Registry, caches all scripts, as a result certain global values will remain persistent. In such a case you might want to use Apache::PerlRun instead , which mimics mod_cgi by flushing the namespace at the every s

Re: multiple developers on one Sever

2004-12-21 Thread Arun pandey
I guess the problem might be with your PerlHandler, coz Apache::Registry, caches all scripts, as a result certain global values will remain persistent. In such a case you might want to use Apache::PerlRun instead , which mimics mod_cgi by flushing the namespace at the every start of request. Th

Re: multiple developers on one Sever

2004-12-21 Thread Pratik
Please provide information about the versions of mod_perl and apache that you are using. If you provide your fully working configuration file, it will be easy to identify the issue. - Pratik -- http://pratik.syslock.org -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://per