Tim Lesher wrote: > I agree with that; the ticket Robin submitted didn't mention running > the task at a specific time, though. If that's what he meant, I > apologize.
In which case I apologize for being unclear - that is what I meant, however I also see the use in being able to use the scheduler to run a background task now - for these reasons: 1. It's the same API for two essentially identical tasks 2. Threading/forking is scary for n00bs - I dunno how TG does it, but I know I would be worried about forking or threading a webserver, because forking it is going to leave two copies in memory, and threading while a DB connection is open brings back scary nightmares from projects past. I would much rather leave it to a tested API. Regardless of that though, I think scheduling a one-time task is a good idea IMO. In at least one of my TG apps I need to perform an action in 24 hours' time (although I don't use the TG scheduler for that as I don't trust the server to run for 24 hours without crashing). -Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
