Hi!
On Tue, Jan 07, 2003 at 09:30:32AM -0000, Gareth Kirwan wrote:
> Hence I'm thinking that I'll need something using the model of require
> species hamster ( from Apache::AuthCookie documentation )
> However I can't find out the significance of the word species ...
>
> hamster is the subroutine in the subclass that will be called and sent $r
> and $args, but where does the notion of species come from ?
it's the other way round:
if you say in httpd.conf
require species hamster
Apache::AuthCookie will call
species() in your subclass and passing "haster" in $args
>From perldoc Apache::AuthCookie:
o authorize()
This will step through the "require" directives you've
given for protected documents and make sure the user
passes muster. The "require valid-user" and "require
user joey-jojo" directives are handled for you. You
can implement custom directives, such as "require
species hamster", by defining a method called
"species()" in your subclass, which will then be
called. The method will be called as "$r->species($r,
$args)", where "$args" is everything on your "require"
line after the word "hamster". The method
should return OK on success and FORBIDDEN on failure.
--
#!/usr/bin/perl http://domm.zsi.at
for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}
