Add example / implementation for coap-handler #107
Merged
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
|
Feel free to target |
chrysn
force-pushed
the
coap-example-using-coap-handler
branch
2 times, most recently
from
27f0ff2
to
34b712b
Compare
|
@chrysn what is the status of this PR? It seems it passes the CI but it is still marked as a draft. Could you rebase on top of latest main? |
|
Rebasing; all I'll change to replace dependency wildcards. |
chrysn
force-pushed
the
coap-example-using-coap-handler
branch
from
34b712b
to
67f2140
Compare
chrysn
force-pushed
the
coap-example-using-coap-handler
branch
from
67f2140
to
1e30db5
Compare
chrysn
force-pushed
the
coap-example-using-coap-handler
branch
from
1e30db5
to
5d048be
Compare
geonnave
reviewed
Nov 4, 2023
| } | ||
|
|
||
| fn main() { | ||
| let mut stack = std_embedded_nal::Stack::default(); |
There was a problem hiding this comment.
@chrysn do you think it would make sense to rename this to network_stack? At first I was thinking it was the program stack 🙃.
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.
The coap-handler trait provides a means for servers to be implemented in a portable way across CoAP stacks. For example, it can be served from the coap crate, or from RIOT-OS. This PR adds an example of how to run an EDHOC server on there.
On the long run, this may spin into a standalone crate that pulls together EDHOC, OSCORE and CWT implementations; for the time being, it serves me as a test bed for making sure that this can be used even on very minimal CoAP implementations. I'm making this into a PR so that a) it's easier to show where requirements such as those behind #104 come from, and b) because I think it may make for a more versatile demo than the current one (at least when duly polished, at which point it'll go from draft PR into PR).
This branch is based on
remove-hacspec, in particular because it depends on #104.