The assumption that the server will send a response to the client after a
move or action XML request is not valid. A watchdog timer should be set
when the response is sent.
This error has occurred and results in a non-responsive client that is
locked waiting for the response from the server.
If the assumption is then made that a request-response pair is not guaranteed
to match all requests need to have a unique ID that is sent with
the response. This way a response that is simply sent late does not interfere
with future move and action messages.
The client may want to have a mechanism for confirming that the action
request has been executed. Alternatively a non-response could be treated
as a failed action or move. This second option should be easier to
implement. The failed response does not occur very often and should not
pose a major problem in game play.
Original issue reported on code.google.com by jjhatf02 on 28 Apr 2010 at 1:54
Original issue reported on code.google.com by
jjhatf02
on 28 Apr 2010 at 1:54