Expose CoAP processing functions#56
Open
mzella-ll wants to merge 1 commit into
Open
Conversation
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.
Summary
This PR renames and exposes the CoAP client/server processing functions.
The generic internal function names are replaced with module-specific names and declarations are added to the corresponding CoAP headers.
Changes
process_response()tocoapclient_process_response().process_datagram()tocoapserver_process_datagram().src/coap/coapclient.hsrc/coap/coapserver.hMotivation
The previous function names were generic and not clearly associated with the CoAP client or server module.
Using module-specific names makes the global symbols clearer and avoids ambiguity. Exposing the functions in the headers also allows other code, such as tests or platform-specific integration code, to reuse the existing CoAP response/datagram processing logic.
Expected behavior
This change should not alter runtime behavior.
The same processing logic is used as before, but the functions are now named more explicitly and declared in the corresponding public headers.
Related issue
Fixes #55