Remeber also that a module gets executed the first time it is called from anywhere. So modules are a very convient place for system wide info.
In my config.py I have datapool = DBPool(PgSQL, 5, 'localhost::xxxxxx') and then elsewhere I from config import datapool conn = datapool.getConnection() .... -Aaron ----- Original Message ----- From: "Edmund Lian" <[EMAIL PROTECTED]> To: "Bobby Kuzma" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, May 11, 2002 12:15 PM Subject: Re: [Webware-discuss] Calling dbPool on AppServer startup > > Bobby wrote: > > >>Where would I put the call to dbPool to establish it's connections so > that > it 1) starts when I start AppServer, and 2) is available to whatever > modules > get loaded in afterward.<< > > You could put this call into one of the context __init__.py files. Any > contextInitialize(appServer, path) method there gets called on context > initialization. The appserver has a hook to shut stuff down prior to exit > too. Look at Application.addShutdownHandler(). > > ...Edmund. > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] > _______________________________________________ > Webware-discuss mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webware-discuss > _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
