Add client-sent keepalives #196
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is analogous to OpenSSH's ServerAliveInterval option.
|
Thank you for the contribution! |
|
I couldn't determine any contributions to add, did you specify any contributions? I've put up a pull request to add @mmirate! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is analogous to OpenSSH's
ServerAliveIntervaloption and is of similar purpose. When the crate user is executing a command that will run for some time without producing output or expecting any input, it becomes difficult to distinguish between "the server has nothing to send" and "the connection to the server has been severed". A periodic keepalive puts an upper bound on how long an unexpected disconnection will go unnoticed in the absence of data traffic.