Okay I thought it will deviate the topic but here I go.
Use the default WebSocketAdapter (that encapsulates NinjaSockets) and connect to host like this:
m_client = new Client(connectionType, host, port, serverkey);
m_socket = Socket.From(m_client);
string user = "someid"
m_session = await m_client.AuthenticateDeviceAsync(user, user);
await m_socket.ConnectAsync(m_session, true, 10);
Then let’s say I had a heartbeat for keeping the socket alive:
async void heartBeat()
{
while(alive)
{
try
{
if (m_socket.IsConnected)
{
Debug.Log("[heartBeat] sending ping");
IApiRpc apiResponse = await m_socket.RpcAsync( "my_ping", "{}" );
}
}
catch (Exception ex)
{
Debug.LogErrorFormat("[heartBeat] Error: {0}", ex);
await Connection.CloseSocket();
}
await Task.Delay( 5000 );
}
}
If I turn off the internet connection, the timeout is not raised until…two minutes? more less. If we check the source code at: https://github.com/heroiclabs/nakama-dotnet/blob/master/src/Nakama/Socket.cs the default time is 30 seconds. Maybe this is not the parameter I’m looking for, but is the only accesible from the client (when I say client I mean the game, not the nakama’s library). And we can’t let the users wait for two minutes for a disconnection notification.
Another thing that happens is if I turn on the internet connection again before this error I receive the following two errors (depending on the send timeout, I think).
The short time one is a task canceled (with a socket closed event), which is weird, for the fact I have to wait to have internet again to receive it.
The other one:
Unable to read data from the transport connection: Connection reset by peer
which is ok and I can try to reconnect it without many problems, but an auto reconnect could be nicer.
I can provide a simple test project if you like
