I managed to reproduce the issue with a non-responding client. The service *should* not wait for the client to answer to position updates, but we apparently do. For that, I attached a branch that tackles the issue by asynchronously handling (lack of) responses.
I managed to reproduce the issue with a non-responding client. The service *should* not wait for the client to answer to position updates, but we apparently do. For that, I attached a branch that tackles the issue by asynchronously handling (lack of) responses.