allow-reconnect #1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "allow-reconnect"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Another step towards allowing reconnections
This implements a ringbuffer that is used to decouple the raw websocket
connection from the messages that the game handler handles.
With this commit, we stop waiting for the websocket connection to be
established before the game starts.
Now, the Connection type is responsible for waiting for the websocket
connection before writing.
Some bugs are still happening:
1. The rejoining client is not told the state of the board
2. Invalid moves are not handled by the client (not sure why though)
3. The still-connected client should be told, that the opponent
disconnected. Then the client should show the passphrase again
Introduce method to send status of board and player
Reconnect works (kind of)
With the right changes in the client, the reconnect works (but only for
the first time).
WARNING:
At the moment, we will create a new player whenever connection wants to
join a private game. This will also clear all the disconnect callbacks
that we set in the player.
c29cdffbc2
toae3e73f711