Support Zeroconf discovery via Avahi #224
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
devgianlu
force-pushed
the
zeroconf-avahi
branch
from
c7e1300 to
bdd84c5
Compare
|
|
devgianlu
force-pushed
the
zeroconf-avahi
branch
from
bdd84c5 to
4d2e207
Compare
devgianlu
force-pushed
the
zeroconf-avahi
branch
from
4d2e207 to
890b193
Compare
|
This will probably work, but now we have avahi as a load time dependency :/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Support using Avahi as the discovery backend instead of the builtin mDNS/DNS-SD implementation. Having multiple services broadcasting mDNS on the same system can be problematic.