-
Notifications
You must be signed in to change notification settings - Fork 130
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
WIP: Switch from jmdns (buggy) to NsdManager
Unfortunately, this limits us to Android 4.1 (API level 16) and up, but this covers over 71% of Android devices currently in use.
- Loading branch information
Jeremy White
committed
Jun 12, 2014
1 parent
c998b54
commit 9fbc29f
Showing
4 changed files
with
149 additions
and
122 deletions.
There are no files selected for viewing
This file contains 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
Binary file not shown.
This file contains 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
This file contains 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
9fbc29f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've switched from nsdManager to jmdns, because nsdManager was buggy. What was the resaon you switched it back?
One example I remember was, when I used nsdManager, it receives two different response from one apple device, and they have different friendly name.
9fbc29f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jmdns is pretty buggy as well.