Re: rfc: allowing more than one mod_perl install - s/Apache2.pm/PREFIX+blib/

Geoffrey Young wrote:
> > The proposed solution:
> >
> > Ditch the Apache2 coexistance workaround altogether and install each 
> > mod_perl into its own PREFIX, preferabbly outside the main perl tree. 
> > Suggested default is /path/to/httpd2/modules/perl, so we have:
> >
> > /path/to/httpd2/modules/perl/lib
> > /path/to/httpd2/modules/perl/bin
> > /path/to/httpd2/modules/perl/include
> > /path/to/httpd2/modules/perl/man
> >
> > This solution requires no extra logic during the build time, since we 
> > simply use the PREFIX MM argument. It also makes the mod_perl 
> > installed base self containing.
>
>
> sounds like a good idea.  however, I don't think I want this as the 
> default behavior.
>
> in the "real" world :), there are probably very few people who are going 
> to want multiple mpms to choose from at the same time - you typically 
> will only roll out one in production (the one that you've proven works 
> for your application) and change it only after significant benchmarking, 
> research, and stresses.

I think we are going to encounter lots of cases where Unix folks will want to 
have both: prefork and worker, (and even perhaps perchild) installed on the 
same machine (not sure about production), so they can perform transition from 
pre-forked apps to threaded apps. And that's the situation I was talking about.

I suppose that this can be done as an addition to the Apache2 solution in the 
main perl tree.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@xxxxxxxxxx http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com