Hi, Yes I was going to have TGScheduler run at intervals to complete any jobs that fail the first time round (as they might, for reasons I can't control).
However, the initial job run is reasonably time-sensitive, so I would like it to get started right as the user POSTs the instructions; but I was thinking that having every web app instance polling the DB at short intervals would be a lot of overhead. That said, if TGScheduler handles the session initiation gracefully, and I'm going to have it running anyway, I could get away with polling a few times a minute and the user wouldn't realistically notice... Thanks for the suggestion! If all else fails, I'll bastardise the session initialisation code from TGScheduler to roll my own :) James On Oct 1, 3:11 pm, NiL <nicolas.laura...@gmail.com> wrote: > Hi, > > have you considered using TGScheduler ? -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.