[EMAIL PROTECTED] (Rodney Broom) wrote:
>I've got this happy little access handler that works just fine. I'm
>loading it like this:
> PerlAccessHandler MyClass
>
>Now I need for it to accept parameters through import(). That would let
>me change the usage to something like this:
> PerlAccessHandle
> The types of parameters I'll pass to this handler will change
> machine-by-machine. You see, I need to run this package on several different
> servers, and need it to know how to configure it's self.
Okay... I don't think I get exactly why this situation makes using
PerlSetVar impossible/imprac
From: "Benjamin Trott" <[EMAIL PROTECTED]>
> Unless I'm missing something rather obvious--or perhaps non-obvious--you
> can't do this. If you provide multiple params to a Perl*Handler, that sets
> up a stacked handlers for that request phase; it doesn't pass parameters to
> the import method in
From: "Carlos Ramirez" <[EMAIL PROTECTED]>
CR> You can use PerlSetVar to set parameters like so:
CR> PerlAccessHandler MyClass
CR> PerlSetVar Param1
CR> PerlSetVar Param2
Yep, that's definately an effective work-around. My biggest concern is the fact
that import() doesn't seem to be getting cal
You can use PerlSetVar to set parameters like so:
PerlAccessHandler MyClass
PerlSetVar Param1
PerlSetVar Param2
in your handler (MyClass) you can call $r->dir_config('Param1') to get
it's value;
-Carlos
Rodney Broom wrote:
Hi all,
Did we forget me? (snif, snif...)
I've got this happy little a
Hi all,
Did we forget me? (snif, snif...)
I've got this happy little access handler that works just fine. I'm loading it
like this:
PerlAccessHandler MyClass
Now I need for it to accept parameters through import(). That would let me
change the usage to something like this:
PerlAccessHandle
