Need keep-alive messages in TCP system
Issue #26
resolved
In working with a client's internal TCP code, I realized that detecting a broken connection is problematic if the app isn't senging messages.
Comments (2)
-
reporter -
reporter - changed status to resolved
- Log in to comment
Added a Keep Alive Ping, sent by the Connection Actor if it receives no message from the Client for 5 minutes. Client replies with a Ping Reply.
Also added a way (as part of initial exchange of messages to negotiate version of Variants) to identify a “Comms schema”. Older code will have zero, and will not use Keep Alives. Version 1.11.0 is Comms Schema 1, with Keep-Alive Ping messages.