Remove throwing TransportException on readLine()
#195
Merged
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.
@ronindesign I am not sure, why we are throwing a
TransportException
here, if there is no data and line anymore.I've developed a client, which stays connected and regulary executes ServerQuery commands like getting the current clientlist and in case of timeouts, it sends a keepalive 50 seconds before the timeout occurs.
However... This
else
code here always causes aconnection lost
within the first 5 seconds after connecting, when the second ServerQuery command gets executed:I've manually removed this
else
part in my localvendor/
directory and then everything is working as expected. I also didn't notice any bad side effects when removing this piece of code. Without this code, my client stays connected for multiple hours without any issues.Could you please double-check this and decide, whether we can simply remove this code or if we need to fix something else?