Optimize Thread usage

[FlyingRatBull]

Optimize thread usage:

• Use IDs in calls to seperate different call returns
• Use threads out of thread pools to run requested functions in
• Let the thread pool be user customisable
• Use an dynamic thread pool with min. 1 thread as default
• Use QFuture and QFutureWatcher to track the state of the executed function
• Use default timeout of 0 (no timeout) for calling functions from client
• Don't cancel runnable if timeout is reached
• Send finishing flag of Runnable atfer completion
• If call to server times out, return in client code but store id of call for later handling of return code

Optional:

• Maybe find a way to use QFuture in client code to return from call() and callRet() directly and watching the return value manually
• Use cancel functionality of QFuture/called to cancel call on server

[FlyingRatBull]

State:

• IDs are used
• Timeouts implemented with default timeout of 30 seconds
• Use per ID locks/waitings for return values

[FlyingRatBull]

QFuture could be utilized through the QFutureInterface but this might be difficult and non persistant through Qt versions.

• Check if persistency is guaranteed by Qt