View Single Post
Old 11-05-2017, 01:29 AM   #13
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by kovidgoyal View Post
It's not that easy. The problem is other device jobs can depend on the results of updating metadata on the device. So you cannot just move the update maetadata job past all other device jobs.
I was thinking that when adding a "Send metadata to device" job, that all "Send metadata to device" jobs that are in waiting status in the queue could be cancelled. I know this would be safe for the Kobo devices. I don't remember seeing anything in the other drivers that would mean it is not safe. I would have said that any that are really just the USBMS driver would have been safe.

Or am I missing some device jobs? From what I see, there are four started by calibre when the device connects: Get device info, Set library, Get list of books and Send metadata. Then there are upload and delete jobs. The Kobo Utilities plugin can start two, but they can be run after the get list job. The Reading List plugin can trigger upload jobs, but that is upload all on a list. I can't think of any other plugins that do or any other device jobs.
davidfor is offline   Reply With Quote