[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:
> PerlAccessHandler MyClass 'extra parameters'
>
>The catch is that MyClass::import() isn't being called reguardless of
>how I load it.
I actually wouldn't expect it to call import() with the given parameter
list, simply because it's documented to do something else. It's
documented to think of the second parameter as another AccessHandler
module, as in chained handlers.
Remember: PerlModule is the way to load new modules. Ordinarily you
should do "PerlModule Blah" to load the module, and then "Perl*Handler
Blah" to actually install it as a handler somewhere. However, in recent
versions of mod_perl, the "PerlModule Blah" will be done automatically
for you if you refer to a previously unseen module as a handler.
To me, the exact behavior you're looking for seems like a bad idea,
because as Benjamin pointed out, it conflicts with the chained handler
syntax. But it seems reasonable that PerlModule might take an import()
list. I'm not sure whether it does so now or not.
------------------- -------------------
Ken Williams Last Bastion of Euclidity
[EMAIL PROTECTED] The Math Forum
