Introduce DNS-SD using mDNS #3351
Open
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.
mg_mdns_listen()signature is changed to the standardmg_*_listen(&mgr, fn, fn_data)mDNS name can then be specified as
fn_data, andfnbe NULL.If
fnis not NULL, it is called for every mDNS record request. Iffn_datais also not NULL, it is checked before callingfn. So:fn_dataworks as before, with the addition of an extra argument, only mDNS, Mongoose replies to a given namefnandfn_data, the user event handler can respond to requests associated to its name, including services, so supporting DNS-SD the easiest way, as Mongoose handles all parsing and response generation; the user only has to match service names to his database.fn, the user event handler is called for every mDNS request, this allows a more flexible way to do whatever weird handling might be needed, as Mongoose does not check for names