|
Calibre 2.xx worked quite well this way - I have a similar setup where one system runs calibre-server and stores the library & database, then another client accesses the library/database over the network.
With the Calibre 3.x content server looking like it will be writing to the database not just reading it, Kovid seems like he's really precluding this type of usage model. I get that's probably Ok for most users, but like the OP, I wish for a few seemingly small concessions which would permit this.
|