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
The INetworkServerListener::ClientDisconnected(kNet::MessageConnection* source) callback is signalled when a connection on the server is fully bidirectionally closed.
However, there does not exist a corresponding event that would get signalled when the network peer only half-closes (write-closes) the connection. Therefore to be able to respond to these remote write-closes and to bidirectionally close the connection, one has to poll to detect this.
Add a signal that gets raised when a connection is write-closed from remote end, so that the code path can avoid polling.
As a workaround, one can poll like this:
// Periodically in application main loop
if (messageConnection->GetConnectionState() == kNet::ConnectionPeerClosed)
messageConnection->Disconnect(); // Peer has write-closed. Write-close from this end as well.
The text was updated successfully, but these errors were encountered:
The INetworkServerListener::ClientDisconnected(kNet::MessageConnection* source) callback is signalled when a connection on the server is fully bidirectionally closed.
However, there does not exist a corresponding event that would get signalled when the network peer only half-closes (write-closes) the connection. Therefore to be able to respond to these remote write-closes and to bidirectionally close the connection, one has to poll to detect this.
Add a signal that gets raised when a connection is write-closed from remote end, so that the code path can avoid polling.
As a workaround, one can poll like this:
// Periodically in application main loop
if (messageConnection->GetConnectionState() == kNet::ConnectionPeerClosed)
messageConnection->Disconnect(); // Peer has write-closed. Write-close from this end as well.
The text was updated successfully, but these errors were encountered: