-
Notifications
You must be signed in to change notification settings - Fork 173
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
How to know when a service goes away? #65
Comments
I have the same question, and also how to unregister the service? Anybody knows if it's supported or not. |
Unfortunately I have not found a way so far, but I did not search very deeply. |
Second this, it's critical for keeping an up-to-date data structure of current clients. We'd need to:
My understanding is that currently none of these "events" are available to the user, in that neither continuously refreshed entries, nor if they're expired through (1) or (2), will emit any new events after the initial discovery. Only the initial discovery is reliably observed. Both are addressed in open PRs #93 and #60. However, they may conflict with each other as-is. For reference, in libp2p#31 both types of disconnects can be detected reliably and without duplicates. Happy to help any way I can. |
@grandcat Could we see the above mentioned PRs reviewed/merged soon? Thanks, everyone! |
FYI I am actively maintaining a fork-of-a-fork at https://github.com/betamos/zeroconf
|
https://github.com/grandcat/zeroconf#browse-for-services-in-your-local-network shows how to browse for services. But how can we catch the event when a service goes away?
avahi-browse -ar
shows such events withThe text was updated successfully, but these errors were encountered: