This repository has been archived by the owner on Jan 14, 2021. It is now read-only.
Fixed unreliable browse resolve #11
Open
Conversation
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
added 3 commits
February 6, 2015 12:27
…times only be able to browse/resolve a few of them
|
Verified that this fix works. I had the same symptom where calling Resolve() would make subsequent discovery not work. |
cerebrate
added a commit
to arkane-systems/Arkane.Zeroconf
that referenced
this pull request
Apr 30, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I found that with more than about 4 devices to discover on the network doing a Browse, Resolve in sequence would often only find about three of them. This was because the Resolve was blocking the Browse from completing so I made it async.