Hi there,
Thanks for this package, I think there's a good compliant dns-sd package still missing for JS. I'm observing something weird, I tried using the browse example, extended to also send a message when the service is no longer active. I'm getting a lot of duplicate active messages (even when the service isn't updated) and unexpected inactive messages, rapidly following each other. I think something is broken in the expiration logic.
I'd expect only a single message to show up when a service becomes active and then no more unless it actually updates.
Output
📡 arcade-C5a@w2d - 10.201.1.7:3031
🔕 arcade-C5a@w2d
📡 arcade-C5a@w2d - 10.201.1.7:3031
📡 arcade-C5a@w2d - 10.201.1.7:3031
📡 arcade-C5a@w2d - 10.201.1.7:3031
📡 arcade-C5a@w2d - 10.201.1.7:3031
📡 arcade-C5a@w2d - 10.201.1.7:3031
📡 arcade-C5a@w2d - 10.201.1.7:3031
📡 arcade-C5a@w2d - 10.201.1.7:3031
📡 arcade-C5a@w2d - 10.201.1.7:3031
... etc ...
Expected output
📡 arcade-C5a@w2d - 10.201.1.7:3031
Hi there,
Thanks for this package, I think there's a good compliant dns-sd package still missing for JS. I'm observing something weird, I tried using the browse example, extended to also send a message when the service is no longer active. I'm getting a lot of duplicate active messages (even when the service isn't updated) and unexpected inactive messages, rapidly following each other. I think something is broken in the expiration logic.
I'd expect only a single message to show up when a service becomes active and then no more unless it actually updates.
Output
Expected output