Separate network communication and UI in qOrbiter
The communication with the server and the communication with the user should happen in two different threads, to make sure both are working independently, i.e. while the device is rendering information for the user, the communication thread can pick up data from the server.
This should happen from the start up, so even while Orbiter startup, the user communication is never controlled by a blocking server communication.