client_listener: Explicitly queue outgoing messages to guarantee order (take 2) #29
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
Spawning a task on each event to send implicitly used tokio as an unbounded queue that doesn't actually preserve order. This could cause issues, such as ConnectionData being sent after the first message, which violates assumptions down the line.
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.
Spawning a task on each event to send implicitly used tokio as an unbounded queue that doesn't actually preserve order.
This could cause issues, such as ConnectionData being sent after the first message, which violates assumptions down the line.
This replaces #28 but avoids re-creating the original deadlock by creating a new task with its own loop.