The /inbox command implemented in the chess server allows players to play one another not necessarily sitting in front of the board at the same time. Both players can send a move to a shared correspondence inbox which will automatically be deleted after thirty days from the last move that was made.
However, the correspondence chess functionality doesn't actually meet the requirement described in the documentation:
The event-driven, non-blocking architecture of the chess server allows to handle multiple concurrent connections in an efficient way. The chess commands are intended to run very quickly almost in real-time.
It is convenient to implement it in the API rather than in the chess server.
The
/inboxcommand implemented in the chess server allows players to play one another not necessarily sitting in front of the board at the same time. Both players can send a move to a shared correspondence inbox which will automatically be deleted after thirty days from the last move that was made.However, the correspondence chess functionality doesn't actually meet the requirement described in the documentation:
It is convenient to implement it in the API rather than in the chess server.
Involved issues are described next:
Keep it up,