This repository has been archived by the owner on Feb 11, 2020. It is now read-only.
Fix wrong receive order of brided requests #40
Closed
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
When the BMC receives bridged requests, "the BMC immediately returns a response to the Send Message command itself". After collection the requested values, it sends the data. This two packages can be received in the wrong order. So, the fix is to look at the responded data and bring the two packages in the right order.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When the BMC receives bridged requests, "the BMC immediately returns a
response to the Send Message command itself". After collection the
requested values, it sends the data. This two packages can be received
in the wrong order.
So, the fix is to look at the responded data and bring the two packages
in the right order.
This should fix Issue #37.