Quote:
Originally Posted by loviedovie
The problem is this, gui apps might crash, killed etc due to memory etc and the user might not know about it or might not have a way to fix the issue remotely. But the services can be restarted automatically. That is why I personally like the separate server app.
I liked having the gui for manipulating "when needed" and let the server running at all times.
|
I'm absolutly with you.. Programs/Processes with the function of offering services to the outside should never rely on a GUI or even an always OS - logged-in User.... what is more, serious server processes mostly run on servers without any graphical UI or on VMs. For this case, calibre-server is generally the right way IMHO
What I'm wondering, too, is, why a seperate server-process (which seems nothing more than a WebServer) is neccessary at all.
Wouldn't it be enogh to write some sort of WebApp (in PHP or whatever language) that deals with the calibre content, offers an OPDS Feed in a completely read-only way and let Apache or NGinx serve it?
Then one could use all the features of a "real" WebServer with all its modules (Basic Auth in many different ways is the first that comes to my mind), so concentrate on the plain "Business Logic" and don't have to deal with how to implement all the HTTP(S) - Protocol / Auth / Security stuff...
But I think, there will be some good reasons, why calibre-server exists..