>>>>> "Jackie" == Jackie Hamilton <[EMAIL PROTECTED]> writes:
> If I have a perl module named "Album.pm" on site 1, and then I
> create another module on site 2 and name it "Album.pm", these seem
> to get mixed up, and sometimes site 1 will show the output from site
> 2's Album module, and vice versa.
This is simply an effect of the way mod_perl works. All requests that
get served by a particular httpd process will share the same perl
interpreter, and that interpreter can only have one version of a
module with a particular name loaded. So if a particular request gets
the output from Album.pm from site 1 or site 2 will depend on which
site that httpd got a request for first (you're not pre-loading the
modules in the parent process, I assume, since then I'd expect you to
always get the same output).
Your options for solving this are limited. The least useful is to wait
for Perl6 and its better handling of module loading :-)
Apart from that, what you need to do is to not serve requests for
multiple sites from the same perl intepreter. Running Mason as CGI
scripts would work, but, well, not exactly fast. There is a page on
the MasonHQ wiki about running from FastCGI, which should get you both
the stand-alone-ness and good speed. It's not exactly a well-tested
setup, though.
--
Calle Dybedahl <[EMAIL PROTECTED]>
http://www.livejournal.com/users/cdybedahl/
"Being stomped on by some sexy commie chick and her perfectly vegan Doc
Martens is not as hot as it sounds." -- babycola
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
