View Single Post
Old 06-13-2011, 06:09 PM   #76
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,444
Karma: 27757438
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Hmm perhaps one way is to allow passing of a previous job parameter to the DeviceJob class. Then the function that launches a job chain should schedule all n jobs at once so that they are atomic. The nth job should check if the n-1th job finished successfully, if so, it should run, if not it should abort.

Sounds reasonable?
kovidgoyal is offline   Reply With Quote