[chaley]

Originally Posted by Bari10

I agree with the OP and have the same request. It is NOT crazy (well, not very crazy) to wish to use wireless connection with a headless server, mainly because of the existence and rapid improvement of CC (Calibre Companion) on android devices. I want to do this, using a headless very low power Dreamplug machine (running debian GNU/Linux) which I'm content to leave running 24/7.

I really don't understand the point.

Calibre's device subsystem is part of calibre's gui. When a device connects, the gui changes to give access to books on the device, to send books to the device, etc. The device is totally passive.

Making the assumption that calibre's architecture does not change, what would you do after connection? The server is headless, so you can't talk to the gui to do "things". The device is passive, so it can't do anything. What is the point of the connection?

The point is that Calibre already includes excellent command line commands and options for this sort of use. For example, if I use the command calibre-server on my little linux box, the calibre server is started, and I can use one of my (e-)readers to browse the OPDS catalogue and read or download books from the linux machine. And I can lave the content server running all the time if I wish.

CC can talk to a headless content server. I recognize that we don't permit specifying two machine addresses, one for wireless connection and one for the content server, but this shouldn't matter if the headless server is on the local network.

What the OP and I want to know is, whether there is a command line command to start the wireless device connection server in a similar way, and if so, what it is.

No, because as mentioned above, the device subsystem is part of the gui. The wireless device cannot start if the gui is not running. Of course, as adoby says the gui could be running a VNC framebuffer, but if this is the case then the gui can be used to start the wireless device.

I am not trying to be difficult. I just don't understand the rationale and use case for starting the wireless device on a true headless server. If devices were to be made active (able to start calibre device operations), then I could see it, but that level of architectural change isn't on anybody's todo list.