Feature nanocoap add resource to handler #15
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
pekkanikander
force-pushed
the
feature-nanocoap-add-resource-to-handler
branch
from
9841748
to
9310e63
Compare
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.
@kaspar030 This is now a minimal alternative to #12. In fact, 09f4ff8 is all I need since now I'm using gcoap, not directly nanocoap. But I think b73efd6 makes sense, too. There lingers still the problem that it should be easy to extend
coap_resource_t, but I can live with this for now.Of course, 09f4ff8 may not work with older compilers. If that is a priority, then it probably will need to be guarded with a suitable
#ifdef.