request-tag: Add in support for sending Request-Tag option with every request #936
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
… request If multiple requests (apart from DELETE) are sent at the same time to the same resource, and the responses need to make use of the Block2 option, there is no way for the server to differentiate between which block set a request (if there is a resource content change) is for unless a Request-Tag is used. Disable this functionality by setting COAP_BLOCK_NO_PREEMPTIVE_RTAG when calling coap_context_set_block_mode(). Request-Tag will still be sent with any request that includes Block1 option.
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.
If multiple requests (apart from DELETE) are sent at the same time to
the same resource, and the responses need to make use of the Block2 option,
there is no way for the server to differentiate between which block set a
request (if there is a resource content change) is for unless a Request-Tag
is used.
Disable this functionality by setting COAP_BLOCK_NO_PREEMPTIVE_RTAG when calling coap_context_set_block_mode(). Request-Tag will still be sent with any request that includes Block1 option.
Addresses corner case issue raised in #793, but did not make it into PR #786 to keep things simple.