Quote:
Originally Posted by eschwartz
|
Yup, it's a new addition to the page.
I'm suspecting that it has to do with the move from Apache 2.2 to Apache 2.4. The In Process server used to work just fine for me using the same distro packages. I've seen other mentions of folk having issues after moving to Apache 2.4 as well.
Here's why I'm not big on running the Calibre server and doing a reverse proxy: It keeps several processes running, each gobbling 115Mb (approx) of resident memory, and 3.3GByte of virtual memory. In my opinion, that's a heavy load to continually run on a server even when it's not being accessed. iirc, the in process server was a tad slower, but would load only on an as needed basis. To me, this is far preferable in a scenario where I'll access it primarily when I'm done a book and looking for something to read.
As for Kovaid, what, if any support he gives is 100% up to him. I expect he has a life outside Calibre and hope he puts that first!
I'd love to see development time put into the in process server, but I realize it's not a feature that most people use, and as such should be prioritized down, especially with things like COPS in existence.
I may look into how to get COPS to play nice with the web browser in my Kobo Aura HD. (Currently, that browser will not download from COPS when the download button is clicked, but downloading the same file / format from the Calibre server works fine)