Bug: For Logon/Logout/Resend/SequenceReset messages we should wait until sent #21
Conversation
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
use default instead of a timer refactor send queued In case of Log On messages block until sent
sai-g
approved these changes
Feb 1, 2024
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.
Issue
When log on request was queued because cannot be send due to connection not ready,
Then it goes through the main session loop which leads to SendAppMessages
But, since session is not logged on yet because the message queued is the log on message, we drop the
toSendqueued messages so we lose the log on message itself.Proposed solution
For important messages like Logon/Logout/Resend/SequenceReset we block until sent.