[cgiapp] app authorization patterns, best practices?

[B. Estrade]

On Wed, Apr 25, 2012 at 03:51:08AM -0400, Nic Zero  wrote:
> No, the main modules don't rely on the drivers being in a close relative path, they just need to be on perl's @INC path.  Take a look at the code of the main modules; it's fairly easy to read and you'll see that it tries multiple path patterns to find your drivers.  Best give your drivers the same name prefix as existing drivers though.

Thanks, yeah. I was looking at the source when it was suggested to me
that I just emulate the namespace path in one of my @INC paths. 

IOW,

I have in - /path/to/my/lib/CGI/Application/Plugin/Authentication/Driver/MyDriver.pm

Now I can configure it to use: DRIVER => ['MyDriver', {arg1=>foo,...}], 

Thank you,
Brett

> Nic
> 
> 
> 
> 
> From: B. Estrade <estrabd at gmail.com>
> To: CGI Application <cgiapp at lists.openlib.org>
> Sent: Tuesday, April 24, 2012 at 7:04 pm
> Subject: Re: [cgiapp] app authorization patterns, best practices?
> 
> I am finally at the point where I am writing a driver, so I have a
> 
> stupid question.
> 
> 
> 
> Do I need to place this into the main module's parent directory in
> 
> order to have Authen/z use them?
> 
> 
> 
> Thanks,
> 
> Brett
> 
> 
> 
> 
> #####  CGI::Application community mailing list  ################
> ##                                                            ##
> ##  To unsubscribe, or change your message delivery options,  ##
> ##  visit:  http://lists.openlib.org/mailman/listinfo/cgiapp    ##
> ##                                                            ##
> ##  Web archive:   http://lists.openlib.org/pipermail/cgiapp/   ##
> ##  Wiki:          http://cgiapp.erlbaum.net/                 ##
> ##                                                            ##
> ################################################################
> 
>