You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.
When adding a service that is already present, it will update the service name with a (2). This isn't registered back in our zeroconf class, so it's going to fall in a heap later. Particularly if we try and shutdown.
The text was updated successfully, but these errors were encountered:
Whoa, this is going back in time. I don't think adding an incrementing numeric counter is part of the standard. From what I recall of what little I've read, there are requirements of uniqueness, and specifications on how it should go about checking for uniqueness, but that is all. Using an incremental counter just happens to be what they do on avahi as well. Is Bonjour the same?
When adding a service that is already present, it will update the service name with a (2). This isn't registered back in our zeroconf class, so it's going to fall in a heap later. Particularly if we try and shutdown.
The text was updated successfully, but these errors were encountered: