nanocoap_sock: implement separate response#20266
Merged
benpicco merged 9 commits intoRIOT-OS:masterfrom May 21, 2024
Merged
Conversation
bd62dee to
6c5df43
Compare
6c5df43 to
91513e0
Compare
fabian18
reviewed
Apr 19, 2024
fabian18
reviewed
Apr 24, 2024
fabian18
reviewed
Apr 27, 2024
de8292e to
63d5a5a
Compare
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
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.
Contribution description
This adds the capability to
nanocoap_serverto send separate response, that is a delayed response outside the CoAP handler.The CoAP handler will first send an empty ACK (if the request was conformable), then some other function can send the actual response at a later time, using
nanocoap_sock_send_separate()with the request context information serialized intonanocoap_sock_response_ctx_t.Testing procedure
A
/separateendpoint was added toexamples/nanocoap_server:Issues/PRs references