Propagate stop request to simulation job
- Added thread in the server to monitor ongoing simulation and reply to corresponsing request
- Added thread in the server to monitor ongoing simulation and reply to corresponsing request
- Server now able to receive a second request while first is running. Only 1 simulation allowed to run, so rejecting further new requests until the previous is finished
- Added STOP request from the client: the ongoing simulation is being killed softly. The result is going to be returned, but not saved since it does not correspond to the request.
- Client is supposed to send each request in a separate thread because the "reply" is blocking
- Returning the result even if simulation has been stopped: WARNING the number of counts is wrong