On 10/12/06, percious <[EMAIL PROTECTED]> wrote: > > Thanks for the info Jorge. Guess I have a reason to upgrade from 9a6. > Erg! ;-). > > I have a database object which holds all py persistant tasks, which I > think is the best way to keep track of everything. You may think about > adding something like tg_scheduler to SQLObject or Alchemy when you do > your implementation instead of keeping everything pickled somewhere. > Perhaps I could sprint on this at Pycon in February if it's not done by > then.... > I don't remenber why exactly but the whole storage idea was drop because of it's many problems. the DB entry was discuss too.
the problem is that you can store the rules to create the tasks but not the task objects, if you look at the way the module is coded something that executes ones a day is one "api call" but ends up creating 7 day task and so on. So what you have is that there will have to be a cache of incomming requests that then will be repopulated everytime tg starts but then how will you delete stuff? we'll need an admin for the list so. isn't it simplier to keep a file with all the tasks to be schedule? the module is flexible enough to schedule things, and the only type of entry that won't work this way is the "one time task" but if you run your script as part of the startup then this will work. > -chris > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
