MobileRead Forums - View Single Post - Question: Calibre upgrade: Large version jump

haertig · 10-10-2017, 03:11 AM

Thanks for the quick replies. I read the webpage on what's new in version 3.0. Unexpectedly, that actually gave me pause regarding doing the upgrade.

I was just beginning to investigate use of the content server. I played with this for a while in my version 2.55. It looked really neat, but some of the documentation I found did not match what I was seeing on-screen. That's when I figured out I was running an old version. Specifically, I was looking at running the content server full-time on my Linux box. But lo and behold, it appears that something new in version 3 says you can't run a server full time, and use the local Calibre interface at the same time. But you can run the server from within the user interface. That means I'd have to leave all of Calibre running full time. Or kill the server, run the user interface, then restart the server. Neither of those approaches sounds appealing. It just doesn't seem "clean".

Hmmm, that kind of defeats the purpose of what I wanted to do (a full time running server). So it appears the trade-off is getting a server with a few more features, but giving up the ability to run that server all the time as a (hopefully smaller memory footprint) daemon process. I'll have to research more, but I think I might actually prefer the older version that (apparently) allows both the content server and the main Calibre interface to run simultaneously, independent of each other. I don't need, and actually don't WANT, for others to attach to the content server and be able to modify anything. I want non-destructive read-only on the content server. This appears to be what version 2 supported, but maybe not version 3 (although I suppose there may be configuration options to make the server read-only).

Again, I'll have to do more research before I decide. But if the main difference between version 2 and 3 is the server, and the new server is less of what I want than the old, it may be best to just stick with the older version I'm currently running.

10-10-2017, 03:11 AM	#4
haertig Wizard Posts: 1,916 Karma: 32620480 Join Date: Sep 2017 Device: PW3, Galaxy Tab A9+, Moto G7	Thanks for the quick replies. I read the webpage on what's new in version 3.0. Unexpectedly, that actually gave me pause regarding doing the upgrade. I was just beginning to investigate use of the content server. I played with this for a while in my version 2.55. It looked really neat, but some of the documentation I found did not match what I was seeing on-screen. That's when I figured out I was running an old version. Specifically, I was looking at running the content server full-time on my Linux box. But lo and behold, it appears that something new in version 3 says you can't run a server full time, and use the local Calibre interface at the same time. But you can run the server from within the user interface. That means I'd have to leave all of Calibre running full time. Or kill the server, run the user interface, then restart the server. Neither of those approaches sounds appealing. It just doesn't seem "clean". Hmmm, that kind of defeats the purpose of what I wanted to do (a full time running server). So it appears the trade-off is getting a server with a few more features, but giving up the ability to run that server all the time as a (hopefully smaller memory footprint) daemon process. I'll have to research more, but I think I might actually prefer the older version that (apparently) allows both the content server and the main Calibre interface to run simultaneously, independent of each other. I don't need, and actually don't WANT, for others to attach to the content server and be able to modify anything. I want non-destructive read-only on the content server. This appears to be what version 2 supported, but maybe not version 3 (although I suppose there may be configuration options to make the server read-only). Again, I'll have to do more research before I decide. But if the main difference between version 2 and 3 is the server, and the new server is less of what I want than the old, it may be best to just stick with the older version I'm currently running.