Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

Duplicate names confuse jmdns #22

Open
stonier opened this issue Nov 13, 2011 · 2 comments
Open

Duplicate names confuse jmdns #22

stonier opened this issue Nov 13, 2011 · 2 comments
Labels
Milestone

Comments

@stonier
Copy link
Contributor

stonier commented Nov 13, 2011

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.

@ghost ghost assigned stonier Nov 13, 2011
@RoundSparrow
Copy link

Is this part of the DNS standard? as I'm still seeing this in late 2013

@stonier
Copy link
Contributor Author

stonier commented Jan 2, 2014

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?

@stonier stonier removed their assignment Apr 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants