in reply to mod_perl and multiple installations of the same code

What little you've described about your application architecture means that you will need to run 4 separate instances of mod_perl.

It would be much better to abstract away the configuration into a cache somewhere, labelled by the application name, and each request goes and retrieves the configuration information for the application making the request. But, that requires rewriting some of your code. Hrmmm ... maybe 4 instances isn't so bad ...

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

  • Comment on Re: mod_perl and multiple installations of the same code