FIx Endlessloop if connection lost #3
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
// Returns it in seconds as float with micosecond precision. We need ms here to compare to timeout ms. So multiply by 1000.
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.
Returns it in seconds as float with microsecond precision. We need ms here to compare to timeout ms. So multiply by 1000.
Before it was the number of thousand seconds since Unix.
Waiting (WaitForData() ) for a delta of 3000 (timeout) resulted to wait for 3000 000 seconds (practical infinite loop), now it's 3000ms.
Now a connection times out.
Did not test for side effects, only looked fast over it, but they are now also in ms not thousand seconds since Unix.