You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no way to cleanly disconnect from the server on the client side: you can just stop the client and the server will detect the disconnection after a few seconds as packets will no longer be received.
The idea is to add a function to the client API that attempts to clean disconnection by sending a specific (library reserved) message (reliably) from the client to the server. Upon reception, the server should probably just close the connection.
On the client side it might be needed to add a "disconnecting" to probably handle the amount of time between sending the disconnection message and actually being disconnected.
The text was updated successfully, but these errors were encountered:
There is currently no way to cleanly disconnect from the server on the client side: you can just stop the client and the server will detect the disconnection after a few seconds as packets will no longer be received.
The idea is to add a function to the client API that attempts to clean disconnection by sending a specific (library reserved) message (reliably) from the client to the server. Upon reception, the server should probably just close the connection.
On the client side it might be needed to add a "disconnecting" to probably handle the amount of time between sending the disconnection message and actually being disconnected.
The text was updated successfully, but these errors were encountered: