[border agent] refactor border agent to use MeshCoP Service state changed callback #2727
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 refactors the BorderAgent module to use the new MeshCoP service state changed callback.
Following openthread/openthread#11215, this PR uses the new MeshCoP service state changed callback to obtain the border agent state, udp port and MeshCoP Txt values. With this PR, the BorderAgent module doesn't need to assemble Txt values from OT itself nor need to subscribe to various Thread state change.
This PR is also intended to decouple the BorderAgent module with OT instance (the RCP architecture) and make it can also work for the NCP architecture.
A new ThreadHost API
BorderAgentSetMeshCoPServiceChangedCallback
is added. In the RCP implementation, it simply usesotBorderAgentSetMeshCoPServiceChangedCallback
. The NCP implementation will be added later. This API is invoked to connect the BorderAgent module with the MeshCoP service state change.