Add handler for ./well-known/core #30
Open
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
Pull Request Test Coverage Report for Build 9798894676Details
💛 - Coveralls |
1 similar comment
Pull Request Test Coverage Report for Build 9798894676Details
💛 - Coveralls |
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.
This PR will implement a handler for
/.well-known/coreto support resource discovery using the CoRE Link Format (see RFC 6690). Once it is finished, it will resolve #2.So far, only the available (unique) URLs are included in the payload that is returned by the handler for
/.well-known/coreas the setting of likectorrtprobably needs a way to defined resources on a "global" level so that the definitions in thecoap innodes don't contradict each other. I will have a deeper look into this while investigating the possibilities for implementing this feature.