Rework timeout logic to try to address the problems described in #5#6
Open
mutability wants to merge 2 commits intodevfrom
Open
Rework timeout logic to try to address the problems described in #5#6mutability wants to merge 2 commits intodevfrom
mutability wants to merge 2 commits intodevfrom
Conversation
* If the input connection is forced to Radarcape mode, then Radarcape status messages are expected immediately; beast-splitter does not wait to see a status message before starting the timer that expects at least one status message per 15 seconds. * New option, --beast-input-timeout, sets a timeout for non-Radarcape connections (in seconds). If no valid message is received within that timeout, beast-splitter disconnects/reconnects. + some internal cleanups
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
If the input connection is forced to Radarcape mode, then Radarcape status messages are expected immediately; beast-splitter does not wait to see a status message before starting the timer that expects at least one status message per 15 seconds.
New option, --beast-input-timeout, sets a timeout for non-Radarcape connections (in seconds). If no valid message is received within that timeout, beast-splitter disconnects/reconnects.