Problem is that in some other environment I can have slower queries than the timeout, so those query will never be able to perform because the Heartbeat basically kills them every time.
It looks like that the timeout "channel" is not running if i'm waiting for a message to a request response socket, is it correct ?
Would be usefull that the Heartbeat would be able to perform also during those exchanges, is it possible to configure it that way ?
Environment
I've been using those parameters to intercept network connection changes, i'm running many devices in an big indoor environment.
socket.Options.HeartbeatInterval = TimeSpan.FromSeconds(15); socket.Options.HeartbeatTimeout = TimeSpan.FromSeconds(5);
Problem is that in some other environment I can have slower queries than the timeout, so those query will never be able to perform because the Heartbeat basically kills them every time. It looks like that the timeout "channel" is not running if i'm waiting for a message to a request response socket, is it correct ? Would be usefull that the Heartbeat would be able to perform also during those exchanges, is it possible to configure it that way ?
Thanks Valerio