Quote:
Originally Posted by kovidgoyal
Actually, the more I think about it, the more it seems that trying to get the GUI to work with a remote server as the backend is a little too ambitiuos. Might be better to just create a "device" that connects to a remote server. That way you can just connect to the server in the GUI and copy books back and forth from the remote server, as you would from a device.
Much easier to implement and while it does not address the use case of running the server and the GUI simultaneously on the same machine, it goes a long way towards addressing the question of how to manage a calibre library on a remote, headless server.
|
That sounds a lot like the wireless device.
Actually, having the remote server connect as a wireless device isn't silly. The protocol and code are stable, it is already well-integrated into calibre, and the functionality is understood. It works with plugins such as reading list. On the other hand, there is the issue of which instance would be in control. For the wireless device, like all devices, the device initiates the connection but the calibre GUI provides the UI. Also, the device protocol doesn't do a very good job of uploading from the device because it doesn't ask the device for known metadata, instead using the metadata in the book.