CoAP: fix possible concurrency of multiple responses #1519
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.
This PR fixes a concurrecyy problem, when two CoAP responses are arriving at the same time.
In the current version of the code, the yielded thread for a blocking request is polled through a callback.
The error scenario is as below:
(in case of block 2 transfers, the block numbers are also affected and were moved to the state structure)
This PR grants, that the CoAP response handler is called immediately after receiving, without waiting for the poll of the yielded process.