Hello Stas,
I'd like to know more about your suggestion of 'running separate mod_perl servers for each host'. Can you elaborate on that? I mean, do you mean to run multiple copies of Apache?
That's correct, Foo Ji-Haw. See: http://modperlbook.org/html/ch12_01.html
In particular: http://modperlbook.org/html/ch12_10.html
You will have a front end light server which will rewrite to backend mod_perl servers.
Though this is good for production. If you have a collision because of the multiple developers using the same server, than a threaded perl with +Parent may work.
Finally, some old mp1 solutions may be of use too: http://perl.apache.org/docs/1.0/guide/modules.html#Apache__PerlVINC___Allows_Module_Versioning_in_Location_blocks_and_Virtual_Hosts Again, not the best solution for production use.
The question is whether you want to use it. Perl w/ithreads not only slows things down and requires more memory, while ok for dev purposes, it will probably won't scale well in production. The reason, cloning a new perl thread under the server with many modules loaded and busy CPU may take... a few minutes.
We should really wait till perchild and/or metux [1] are completed, which is when you will be able to use a scalable solution for independant vhosts. The problems is that it doesn't seem that anybody is working on those.
The best solution for now if you have conflicting namespaces, is to run separate mod_perl servers for each host.
[1] http://nibiru.borg.metux.de:7000/wiki.mpm/
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com