Support multiple FreeRTOS mDNS instances - #57
Draft
bgewehr wants to merge 1 commit into
Draft
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.
Problem
Follow-up to #35 and complementary to the per-
DeviceLocalevent isolation in #44: the FreeRTOS mDNS backend still routes asynchronous query completion through one process-globalmdns_inst. With multiple OpenEEBUS services, only the last-created instance receives query completion. Stopping one instance also callsmdns_free(), which tears down the daemon shared by the other instances and the host application.Change
mdns_query_ptr()API from each instance's existing browser thread, removing the global callback owner;No public OpenEEBUS API changes are introduced.
Verification
The target compile used Espressif mDNS 1.11.0, where multiple service instances are enabled by default.