-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Darwin] Add the ability to browse operational nodes with the device scanner #27940
base: master
Are you sure you want to change the base?
[Darwin] Add the ability to browse operational nodes with the device scanner #27940
Conversation
|
I have updated a little bit the code from |
|
ceb3087
to
2c0c0d2
Compare
2c0c0d2
to
5c94b8e
Compare
5c94b8e
to
8e372a3
Compare
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
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.
Changes requested - I am afraid this looks to bypass comments in #26718 by creating a new PR.
Overall I need to understand why we would like to browse operational nodes - that seems to create extra traffic for nodes that are inactive.
Please add some description of use case and explanation how we measure "success". It also needs unit tests (or I guess integration tests in this case because of the level it is at) and implementations in more than just darwin since it is a global thing - avahi and minmdns seems needed. I am worried about minmdns overhead and complexity.
@andy31415 I don't understand this part. What definition of "inactive" are we using here? Fundamentally, browsing for operational nodes is a way to get notified when a node that was not on the network starts being on the network. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Problem
There is no underlying API for the
DnssdBrowseDelegate
to resolve operational nodes.This PR add such supports for the
darwin
backend as well as a command inchip-tool
for it.This is an attempt to get #26718 to move forward to the
DnssdBrowseDelegate
. The benefit of it is that is allow to monitor nodes for long lived operations, such as addition and removals.