Oxide

  1. Bug #1462664
  2. Comment #41

Comment 41 for bug 1462664

Revision history for this message
Thomas Voß (thomas-voss) wrote :

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.