fix SetReadDeadline() has no effect after AcceptKCP() has been called #193
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.
kcp-go/sess.go
Lines 913 to 918 in 88fc14a
Here
var timeout
is fixed, thus subsequent calls toSetDeadline()
afterAcceptKCP()
will not be able to change the listener's timeout.From a naive understanding of the go document, calling
SetReadDeadline()
should be able to extend the deadline of the underlying connection.https://golang.org/pkg/net/#PacketConn