View Single Post
Old 07-06-2011, 03:47 PM   #51
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,449
Karma: 27757438
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Quote:
Originally Posted by ApK View Post
I want to make sure I'm clear: using a networked backend is optional, but the architectural changes that enable it, which prevent the Apple driver from directly accessing a file in the library, as it had done until now, are not optional, and GRiker's Original post info will apply to anyone who uses 0.8.8 or higher whether they use a network backend or not, correct?

ApK
Yes. And let me repeat, that the old architecture which had itunes directly referencing files in the calibre library, was IMO, not the best. For example, if you change the title/author of a book that you had previously sent to itunes, in the old architecture, its path on disk would change and itunes would lose track of it. Or on windows, where files are locked whenever they are opened, if you try to do some operation on a file while it is open in iTunes, the operation would fail. Conversely if calibre is doing something to the file and itunes tries to open it, it would fail.

So, I think this change is a desirable thing, regardless of the network backend.

Last edited by kovidgoyal; 07-06-2011 at 03:51 PM.
kovidgoyal is offline   Reply With Quote