View Single Post
Old 06-28-2017, 07:33 PM   #44
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by snoopy_1978 View Post
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..
Minimal PHP webapps that look at your calibre library and serve files, already exist. calibre-server does much more than that, however, and I don't really understand why you care which language it uses to implement complex read/write operations that query a database and can modify files as needed in-transit (cf. plugboards) etc.

And it also needs to implement auth, protocol, etc. because not everyone wants to set up an apache instance in order to use calibre's Content Server.

Quote:
Originally Posted by snoopy_1978 View Post
The idea to extend the calibre-server (or the WebFrontend it provides) with more and more functions and features is very good I think, I like WebApps at all.
But I don't understand the need of wrapping the WebFrontend with a self implemented webserver and not just take standard technologies (Nginx/Apache + PHP/OtherLanguage + some DB like in thousands of other Desktop like WebApps nowadays) and just concentrate on the WebApps core functionalities...
This is complete and utter nonsense. There are many server applications powering important things on the internet, which are self-implemented in, for example, python rather than being written in PHP.
eschwartz is offline   Reply With Quote