keepsimple1
keepsimple1
No problem! I think we should improve the doc for the users to discover this feature more easily. Update: opened PR #359 .
I think the main feature request of this issue is done. If there is a need to support a custom function plug-in for name changes in future (see [early comment](https://github.com/keepsimple1/mdns-sd/issues/264#issuecomment-2878687042)),...
As we use `flume` channels, we are limited to its API. My understanding is that such API would need an async timer, and it's tricky for `flume` to support async...
> If I would be able to create a new general-purpose API which accepts an external timer, defined outside and passed as an asynchronous closure, would you accept that kind...
> It seems that when ServiceInfo addresses contains both IPv4 and IPv6 addresses, two SRV announcements are made, one with the A record and another with the AAAA record. Yes...
> However the last time it is raised, the number of addresses is back to just the IpV6 addresses. Could this be the root of the issue? Yes, this looks...
> The problem sometimes appears simply by clicking the “Browse” button in [hrzlgnm/mdns-browser](https://github.com/hrzlgnm/mdns-browser) without selecting a specific service type. Did you mean it sometimes does not show services available, or...
> Now it also makes sense to me to separate IPv4 and IPv6 ServiceInfos and per interface like Avahi does. That would make the structure more cleaner. Could you elaborate...
> > But how do we want to do that without introducing a breaking change? > > I see the following option here: > > * add `with_interface_id()` constructor which...
> `InterfaceId` being defined as: > > ```rust > struct InterfaceId { > name: String, > index: Option, > } > ``` > > If you don't object. No objections....