Mason and potential disaster discovery

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

Replies are listed 'Best First'.
Re: Mason and potential disaster discovery by perrin (Chancellor) on May 29, 2009 at 14:44 UTC
VirtualHosts normally share a Perl interpreter. You can set up mod_perl2 to run separate ones for each VirtualHost, but it will use a lot more memory. It would be better to fix your code.	[reply]
Re^2: Mason and potential disaster discovery by zdzieblo (Acolyte) on May 29, 2009 at 15:29 UTC
For the moment I'm testing 'PerlSetVar MasonInPackage MySeperate::Namespace' which in theory should separate my globals. But thanks for bringing that separate Perl interpreter idea.	[reply]
Re: Mason and potential disaster discovery by Anonymous Monk on May 29, 2009 at 03:13 UTC
global means they're shared	[reply]
Re^2: Mason and potential disaster discovery by zdzieblo (Acolyte) on May 29, 2009 at 10:09 UTC
umm.. global also means not shared, imagine script a.pl and b.pl, they both got globals in them but it doesn't necessarily mean that a.pl can read b.pl's data ;-)	[reply]
Re^3: Mason and potential disaster discovery by Anonymous Monk on May 29, 2009 at 11:04 UTC
If they're running under apache/mod_perl, it means they're shared.	[reply]
Re^4: Mason and potential disaster discovery by zdzieblo (Acolyte) on May 29, 2009 at 13:42 UTC
Re^5: Mason and potential disaster discovery by Anonymous Monk on May 29, 2009 at 13:45 UTC