Make client requests non blocking

[UsualSpec]

autopower/client/client.cc

Line 631 in 1911af7

while (serverApiStream->Read(&sRequest)) {

is executed in one thread only. To allow responsiveness, we should rewrite the code such that we execute management functionality in a separate/separate threads. Then the client remains responsive for new commands from the server and can already start them if possible. This could fix #23 potentially.

Suggestion:

1. If a new sRequest arrives, put it into a commands queue
2. In another thread consume the queue and issue the respective function in a separate thread.
3. Send response to server

[romain-jacob]

Somewhat related: why do we send a request to the client in order to get the IP? Why not simply save the IP in the database when the client registers to the server? Sounds like it would be a lot simpler, no?

And if the IP changes, the client would anyway register again to the server I suppose, since changing IP address (almost always) implies we lost network connectivity. Or am I missing something?

[UsualSpec]

Ok. Checkout #29
This could be a fix. We're using boost now.
I tested it and it seems to work. However as it introduces concurrency now, this could introduce concurrency bugs. I wrote the client to be thread safe, but there could be oversights.

[romain-jacob]

Okay. I don't have the competence to judge by just looking at it if that makes sense. I trust you to keep testing until you're confident it can be merged.

[UsualSpec]

Another thing (no need to respond, just for documentation).
https://www.postgresql.org/docs/current/plpgsql-trigger.html#PLPGSQL-TRIGGER-EXAMPLE --> using a trigger to create an entry in the clients and measurement tables if necessary.