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
For testing client logic to handle KeepAlive Messages it would be helpful to have an option with the CLI to suspend or interrupt the outgoing messages.
I'm not certain of the causes or conditions that could cause a real server in production to stop sending the messages, but from the documentation it sounds like the connection itself is still considered open (or at least has not received an explicit close).
Ideally, the option with the CLI would stop sending the Keepalive Messages to an existing client but not prohibit establishing new connections which would receive the messages as normal. Perhaps specifying the SessionID to suspend?
Disclaimer
I agree
The text was updated successfully, but these errors were encountered:
Tell us about your feature request
For testing client logic to handle KeepAlive Messages it would be helpful to have an option with the CLI to suspend or interrupt the outgoing messages.
I'm not certain of the causes or conditions that could cause a real server in production to stop sending the messages, but from the documentation it sounds like the connection itself is still considered open (or at least has not received an explicit close).
Ideally, the option with the CLI would stop sending the Keepalive Messages to an existing client but not prohibit establishing new connections which would receive the messages as normal. Perhaps specifying the SessionID to suspend?
Disclaimer
The text was updated successfully, but these errors were encountered: