Support granular conditions on service registration

[twizansk]

We would find it very useful to be able to register services with specific conditions:

• associate them with with specific interfaces.
• return only link-local ips

for example, for security reasons certain IoT devices are only allowed to communicate with each other over approved network interfaces. clients should not even be provided the ips for other ifaces during service discovery.

I've pushed a draft pr: #398

@keepsimple1 if this looks like a reasonable update to you, I can finish up the pr (cleanup, tests, etc.) and take it out of draft

[keepsimple1]

Thanks for the PR, I've provided comments there.

Btw, just checking, would enable_interface and disable_interface work for your use case? I understand they are for the service daemon, not ServiceInfo, but wanted to check with you.

[twizansk]

Thanks for the PR, I've provided comments there.

Btw, just checking, would enable_interface and disable_interface work for your use case? I understand they are for the service daemon, not ServiceInfo, but wanted to check with you.

I don't think that would work, unless I'm missing something. our goal is to enable specific services on specific interfaces. so for example browsing for _<super secure service>._udp should return only the ethernet ips but browsing for _<public apis>._tcp should return everything

[keepsimple1]

PR merged! 🚀