examples: Add traits based CoAP example #241
Draft
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.
Unlike the server, this is using embedded-nal-async, because that's what a CoAP implementation exists for that can do client as well. (I may update the server side to use that as well instead of the blocking version, but they don't conflict).
Having a server and a client that work with embedded CoAP stacks is an important step towards having a pair that can exchange requests over 6LoWPAN on embedded hardware (apart from the executor setup and possibly the random source, both should work on RIOT just fine).
PR marked as WIP as I'd like to have authz in there, and am struggling with it. (The only working client side example I have is in C, and that appears to do the static-static derivation manually from reaching deep down into the state, but that can't be it, given how smoothly the server side works).