On Sun, 2007-04-02 at 19:58 -0500, Mark Ramm wrote: > This has come up on the list once before, and I answered the same way > on your other new thread, but I think the best answer was to use the > TurboGears scheduler to hit the DB regularly. > > http://docs.turbogears.org/1.0/Scheduler
Yeah cool, I was wondering whether the mysql guys had made this unecessary yet. The catch with the schedular method that I don't like is that it depends on CherryPy staying up. So if you're using the mod_proxy/mod_rewrite of a 500 error message that wakes up CherryPy in case of a problem, then a cron job hit should wake up CP and then hit mysql. If CP goes down and you're using the schedular, then it won't get woken up until a user hits your site, correct? So mysql could go to sleep still. I think the cron job is kind of ugly, but at least it makes sure they both stay up relying only on cron and wget. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
