Jonathan Vanasco wrote:
Unless I'm confused, I've been doing that for years without issue.
I routinely have
P2XLP::$package - base namespace
MyApp::$package - @ISA( P2XLP::App::$package )
Are you saying that you have multiple MyApp::Foo packages running under the same
mod_perl
On May 11, 2008, at 2:52 AM, Marc Lambrichs wrote:
Here's my view: they create a parent App::Handler and in every
virtual host they create a Site::Handler which has App::Handler as
base. My first guess is that under mod_perl you don't know which
Site::Handler will be called. Ofcourse, at
On Sun, May 11, 2008 at 2:52 AM, Marc Lambrichs
[EMAIL PROTECTED] wrote:
Secondly, what if we're running the cgi under speedycgi?
You can do this with FastCGI if you run a different FastCGI backend
for every virtualhost. The same thing would work with mod_perl if you
run a different
Creating packages with the same name for multiple sites is generally a
recipe for confusion. Following what Michael Peters said, the better way
will be to create a properly namespaced package instead.
But in the event that the right thing cannot be done, you can consider
creating a new
I've taken over some code for a client. They've built a framework that
used to run under mod_perl and changed it later, because of problems
they had - what problems remains unknown - to cgi. Ofcourse I'm curious
why they changed it. Here's my view: they create a parent App::Handler
and in
Marc Lambrichs wrote:
So, my first question is: am I right?
Yes. And it's not a mod_perl thing, it's a Perl thing. You can't have multiple
modules with the same name. Now people try this more under mod_perl because they
think different requests behave differently, but that's not the case. Each
