Making listening network connections opt-in

[Bastian Germann]

On trunk OpenLP establishes listening network sockets for the projector component, the web remote control, and the websockets API. I cannot disable any of them. In version 2.4.6 there are no listening connections if you do not explicitly enable the remote control.

The user should be able to disable the connections and they should be disabled by default (opt-in). If you do not want to disable by default, the default listening IP should at least not be the world (0.0.0.0) but localhost (127.0.0.1).

[Ken Roberts (alisonken1)]

Speaking only about the projector -

The reason 2.4 did not open a socket and listen for projectors is because PJLink did not have an option to broadcast projector status packets - by design, PJLink version 1 would only talk to controllers that had opened a TCP connection directly to the projector. Unsolicited selected status changes in the projector sending UDP packets to the controller were only added in PJLink version 2 (which came out after OpenLP had frozen 2.4.6 as the last 2.4 series)

I understand and agree with your assessment of the projector listening for projectors - there would be no sense in listening on localhost for the projector code since your computer is typically not a projector - unless you're using a local emulator to test functionality.

I will add an enable/disable option in the projector settings.