Send MQTT packets atomically in a single socket write#49
Merged
python36 merged 1 commit intopython36:masterfrom Mar 25, 2026
Merged
Send MQTT packets atomically in a single socket write#49python36 merged 1 commit intopython36:masterfrom
python36 merged 1 commit intopython36:masterfrom
Conversation
Previously the fixed header and payload were sent in separate async socket writes. Since each write awaits, other tasks could interleave writes on the same socket, potentially corrupting packet framing. This change builds a single contiguous buffer and sends it in one async write call to ensure packet atomicity. Signed-off-by: Takeyoshi Kikuchi <kikuchi@centurysys.co.jp>
Owner
|
Merged! Thanks for the contribution, @centurysys |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously the fixed header and payload were sent in separate async socket writes. Since each write awaits, other tasks could interleave writes on the same socket, potentially corrupting packet framing.
This change builds a single contiguous buffer and sends it in one async write call to ensure packet atomicity.