Add option for configuring connection response timeout #719
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
ethouris
added
[core]
maxsharabayko
requested changes
Jun 3, 2019
|
This is actually an inactivity timeout. RSPTIMEOUT may be confused with the existing RCVTIMEO, Regarding TIMEO vs. TIMEOUT I think the initial proposal was for consistency with the other timeout options (SNDTIMEO, RCVTIMEO, CONNTIMEO). It is a choice of consistency vs. clarity. |
|
maxsharabayko
approved these changes
Jun 5, 2019
|
@jeandube your decision. |
|
@maxlovic Everything is fine with me. |
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.
New option:
SRTO_RSPTIMEOallows to configure "response time", that is, the longest tolerable time during which agent receives no packets from peer. Upon passing of this time the connection is considered broken.