On Wed, Oct 21, 2009 at 7:20 AM, Rolf Schaufelberger wrote:
> You could hide these vhosts behind a proxy, and +Parents just works fine
> with different lib direcories.
> Following the mod-perl performance guide it is recommended to split your
> app to frontend an backend apache and so
> you can
Am 21.10.2009 um 12:00 schrieb Torsten Foertsch:
On Wed 21 Oct 2009, Alan Young wrote:
http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_
Unfortunately the Parent option works only in vhosts. But I believe it
could be hacked to work also for directory containers. Of course
Per
On Wed 21 Oct 2009, Alan Young wrote:
> http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_
Unfortunately the Parent option works only in vhosts. But I believe it
could be hacked to work also for directory containers. Of course
PerlPostReadRequest, PerlTranslation and PerlMapToStor
l Message -
From: "Devin Teske"
To: "Brad Van Sickle" ; "Adam Prime"
Cc: "Alan Young" ; "Michael Peters"
;
Sent: Tuesday, October 20, 2009 4:51 PM
Subject: Re: Custom INC per-directory
Hehe, it does seem kind of looney, doesn't it?
In a
essary, always getting the right module, whether it's provided
by cache or not.
--
Devin Teske
- Original Message -
From: "Brad Van Sickle"
To: "Adam Prime"
Cc: "Alan Young" ; "Devin Teske"
; "Michael Peters" ;
Sent: Tuesday,
ng a copy.
----- Original Message -----
From: "Alan Young"
To: "Devin Teske"
Cc: "Michael Peters" ;
Sent: Tuesday, October 20, 2009 4:05 PM
Subject: Re: Custom INC per-directory
Wouldn't using the Parent option (
http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_ )
work better for what you're trying to do?
--
Alan
I don't know the specifics of your project so it's quite possible that
I'm missing something, but this all seems like an incredibly bad idea.
Sure you can knock some cringe inducing code together and get it to
technically work, but the very fact that you need to resort to these
sort of unortho
Alan Young wrote:
Wouldn't using the Parent option (
http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_ )
work better for what you're trying to do?
Parents requires vhosts, which he said he doesn't want to use.
Adam
Wouldn't using the Parent option (
http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_ )
work better for what you're trying to do?
--
Alan
On 10/20/2009 05:24 PM, Perrin Harkins wrote:
Performance will suffer, but it will work for most code.
Right. Your Perl interpreter will be persistent, but none of your code
will be cached and thus every module you use will be reloaded on every
request. It also means you can't do pretty stan
On Tue, Oct 20, 2009 at 5:16 PM, Devin Teske wrote:
> the problem is that 'require' and 'use' want to conditionally not re-
> import the library based on the module name (which doesn't change)...
>
> ...the solution is to not use 'use' or 'require' and instead beat down
> on the INC hash yourself,
Ok, my last attempt, which involved using blocks, didn't work
either (and I know why).
Here's the final solution that is working 100% of the time.
So...
the problem is that 'require' and 'use' want to conditionally not re-
import the library based on the module name (which doesn't change)...
Yes, but that's a horrible solutions (thinking "utter nightmare" when it
comes to system administration, et. al.).
I've currently got it working with this (which seems to be MUCH more
elegant, only requires a single Apache server, no virtual-hosts, is
directory-based, and requires no special conf
On 10/20/2009 01:06 PM, Devin Teske wrote:
I've been trying for what feels like months now to find some way to have
two directories specify the same module name to PerlInitHandler but to
use two different modules.
This isn't a limitation of mod_perl but a limitation of Perl. You can't
have 2
Well, I was thinking I could get away with something like this...
foo's .htaccess:
use ModPerl::Util;
ModPerl::Util::unload_package(MyAuth::Authnz);
unshift(@INC, '/modules/foo');
push @PerlInitHandler, 'MyAuth::Authnz';
bar's .htaccess:
use ModPerl::Util;
ModPerl::Util::unload_p
> For example, I'd like to be able to have:
>
> File 1: /usr/foo/.htaccess:
> PerlInitHandler MyAuth::Authnz.pm
> # We want this to load /modules/foo/MyAuth/Authnz.pm
>
>
> File 2: /usr/bar/.htaccess:
> PerlInitHandler MyAuth::Authnz.pm
> # We want this to load /modules/bar/MyAuth/Authnz.pm
Th
Hi there, list,
I've been trying for what feels like months now to find some way to have
two directories specify the same module name to PerlInitHandler but to
use two different modules.
For example, I'd like to be able to have:
File 1: /usr/foo/.htaccess:
PerlInitHandler MyAuth::Authnz.pm
# We
17 matches
Mail list logo
