in reply to issues with module versions

I think you have several options. We often run different mod_perl apps on the same box using separate httpd.confs and separate apache instances. Though ours don't, each of those confs could include different use lib paths. This seems cleanest (to me).

Phil

Replies are listed 'Best First'.
Re^2: issues with module versions
by pajout (Curate) on Oct 06, 2005 at 14:04 UTC
    Thanx for answer, we use this way too ;0) But it consumes more memory - apache childs, db connections etc...
[reply]
      You're right it will consume more memory, but most of this memory is shared (well, in *nix land it is, even in some OSes have problems reporting shared memory).

      You can reduce the number of apache children (and db connections) you need per application by running a simple lightweight proxy in front.

      -- More people are killed every year by pigs than by sharks, which shows you how good we are at evaluating risk. -- Bruce Schneier
[reply]
        Yes, I know... httpd scaling has some limitations, especially, when non-shared part of httpd-children takes ~15M (which is not good state, I know).
        Imagine, that two similar legacy applications run under Apache, using the same db and sharing some perl modules. But, acidentally, one of them uses old version of MyFamily::Session and the second uses newer version of this package...
[reply]

In Section Seekers of Perl Wisdom