Thread: CC Cloud
View Single Post
Old 06-13-2015, 09:03 AM   #23
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,463
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Question about checking covers

Do any of you have an opinion on how often I should check if covers have changed? I can see any of
  1. every time the cover is accessed
  2. the first time after "CC Cloud" (whatever it is called) is started
  3. every so often (once per hour, once per day)
  4. every time the user looks at book details
  5. only the first time the cover is shown
If works acceptably well with #1, but I am concerned that the cloud service might decide CC is checking to frequently and slow down any responses. I am also not convinced that checking so often is necessary.

One factor to consider is how easily a user can understand what is happening. Another factor: things can get messy if the user is simultaneously changing the library with calibre and using CC Cloud. Currently the metadata.db is checked with CC Cloud is started, which means that the database and potentially the file system in CC Cloud would be different from the database in the cloud until CC Cloud is stopped and restarted. Should I periodically check whether metadata.db has changed? If so, how often?

The two factors make me partial to #2, where the behavior has the same explanation. Of course #2 doesn't deal with file system/metadata.db changes while CC Cloud is running, but I don't see any way to handle that gracefully.

Of course there will be a way to empty the cache, but that seems to be a big hammer.
chaley is offline   Reply With Quote