avo has asked for the wisdom of the Perl Monks concerning the following question:

Good day monks, I have a mod_perl environment running couple of applications. They all have the following:
use lib '/wwwroot/applicationX/';
use stemp;

My problem is that I would like to have stemp.pm in each folder applicationX,Y,Z, etc. That does different things. The mod_perl however uses the first loaded stemp.pm as package stemp for all other instances... regardless that for instance /wwwroot/applicationY/stemp.pm is completely different thing.
Please give me an idea how to go arround this problem. I don't want to name the modules different, I just want each application to reffer to the module that is in it's own folder.

Thanks

Replies are listed 'Best First'.
Re: mod_perl namespace
by pajout (Curate) on Jul 03, 2007 at 09:52 UTC
    I think that different naming is less painfull then fiddling modules, specially in the situation, when that modules are really different...

    If they are your modules, my idea is to prepend namespaces unique by applications, to distinguish MyModule.pm, for instance,
    ...appX/perl-lib/APPX/MyModule.pm
    ...appY/perl-lib/APPY/MyModule.pm
    -> from mod_perl perspective, you have two different modules, APPX::MyModule and APPY::MyModule
    ->contrary, shared modules can be located in ...appX/perl-lib directory.

[reply]
      So, it looks like you have to require "the file" not use() the module to accomplish this. This looks impractical to me.
[reply]
        No. I assume that @INC contains both paths (.../applicationX/perl-lib, .../applicationY/perl-lib) and modules are used: 
        #for X application
use APPX::MyModule;

        [download]
[reply]
[d/l]

Back to Seekers of Perl Wisdom