[cgiapp] Newbie: cgiapp_preinit vs. setup?

[Kevin P. Fleming]

I've just spent most of the day learning about CGI::Application, 
Template::Toolkit and all this other cool stuff for an application I'm 
building (well, I had started building without knowing about these 
tools, now I'm restarting the build :-).

My application will need to use CGI::Session for storing information 
about the user and will also be using DBI to talk to a MySQL database. 
Is there any common wisdom out there about performing the session 
setup and DBI setup in cgiapp_preinit() vs. setup()? I suppose if I 
had any intentions of superclassing this app in the future I could 
have this stuff in cgiapp_preinit() and then it would be shared by the 
other versions of the app, but I don't really see that happening...



---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[EMAIL PROTECTED]/
             http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]