|
|
|
| No such thing as a small change | |
| PerlMonks |
Re: User authorization and design of larger web/intranet applications.by MrCromeDome (Deacon) |
| on Oct 10, 2005 at 10:00 UTC ( [id://498807]=note: print w/replies, xml ) | Need Help?? |
This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.
cgiapp_prerun() is not the best place to do things such as creating a database connection or initializing most plugins. You'd be better off doing those things in the cgiapp_init() method of your base class. For module-specific configuration, use the setup() method. cgiapp_prerun(), however, is a good place for authen/authz checking. Speaking of authen/authz, I'm sure you are aware of Cees' excellent CGI::Application::Plugin::Authentication plugin. Authorization has been planned, but as far as I know he is still working on it. Check the CGI::Application mailing lists for more information. And, of course, you can look for CGI::App help at #cgiapp on irc.perl.org :) (I know you have) Good luck!MrCromeDome
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||||