No race condition... if the flag is set, the system will not - generate config caches - check if config files exist - check if cached versions exist - check if anything is up to date The setting is only supposed to be used if you know that all config files are already generated and up to date. Purpose is to boost production environment performance.
By the way, I put per-context config files on my todo list for 0.11. This will be great. You'll even have a per-context config.php, so you can have "devel" and "production" contexts. And separate databases. And, and, and, and. Cool, eh? - David > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Veikko Mäkinen > Sent: Wednesday, November 23, 2005 11:05 AM > To: Agavi Development > Subject: Re: [agavi-dev] The merging-my-branch discussion > > David Zülke wrote: > > Hi folks, > > > > I'd like to hear your opinions on the changes I made to my branch > > The race condition problem is, or is going to be, a pain in the butt... > but maybe we'll go ahead with this and see how big of a problem it'll be > and try to find a solution to it? We also discussed some time-to-live > option for cache files (AG_CACHE_TTL?). Could these two be integrated? > > Other than that I have only one question - how do I merge David's branch > into mine so that I can get David's work into action :) Brilliant work. > > > -veikko > > _______________________________________________ > agavi-dev mailing list > [email protected] > http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev _______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
