perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Peters <mpet...@plusthree.com>
Subject Re: refactoring client's decision
Date Sun, 11 May 2008 12:08:33 GMT
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
request will hit the same long-running Perl interpreter.

> Secondly, what if we're running the cgi under speedycgi?

I don't know. I haven't used speedycgi. FastCGI seems to be what most people
prefer these days, but I don't know about it's problems either.

Typically how people solve this under mod_perl is to give each client it's own
namespace. So you'll have Client1::App::Handler, Client1::Site::Handler,
Client2::App::Handler, Client2::Site::Handler, etc. Another alternative is to
run a separate mod_perl backend apache for each client and just have the front
end proxy redirect to the right one based on the virtual host. Depending on how
many clients you have though, that could get a little wasteful.

-- 
Michael Peters
Plus Three, LP


Mime
View raw message