While building your first application, that may not make use of a Super Class, it doesn't make much difference where you put the session / db connect code.
However, as you build more and more apps, you'll probably end up creating a Super Class that will hold much of your common code (session, db connect, configuration loading, etc) and each application that makes use of that super class will have it's own setup method. Each applications setup method will then only be used for setting up the run modes for that app, and maybe hold some additional application specific 'init / setup' code. So in short, start getting into the habit of using cgiapp_init() now, and you'll thank yourself for it later. --- Steve Comrie ----- Original Message ----- From: "Kevin P. Fleming" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, August 24, 2003 10:34 PM Subject: Re: [cgiapp] Re: Newbie: cgiapp_preinit vs. setup? > Mark Stosberg wrote: > > > You may also find this document on the "order of operations" of CGI::App > > execution useful: > > > > http://twiki.med.yale.edu/twiki2/bin/view/CGIapp/OrderOfOperations > > > > I did find that useful; in fact, it's what lead me to believe that > there was no particular advantage in one or the other. --------------------------------------------------------------------- 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]
