[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [patch #9555] Add MDNS probing
From: |
Jens Nielsen |
Subject: |
[lwip-devel] [patch #9555] Add MDNS probing |
Date: |
Tue, 6 Feb 2018 14:31:39 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 |
Follow-up Comment #6, patch #9555 (project lwip):
Hi Axel,
Yes you're right, I'm already losing track of my own patches but
mdns_resp_start() shouldn't be necessary if all this gets approved. Before
this commit you were supposed to call mdns_resp_announce() when all services
had been added but this should also not be necessary. I have updated some of
the documentation in patch 5 but this needs to be revisited again, I see
UPGRADING mentions mdns_resp_announce()
I have also prepared two new api functions to allow renaming netif hostname or
service name so user won't have to call mdns_resp_remove_netif() and add
everything again (which would trigger igmp leave/join). I will test it within
a couple of days and upload another patch...
With this the only thing I'm not happy with in the api is
mdns_name_result_cb_t which doesn't tell the user whether a conflict was on
the netif or a service, or _which_ service. I don't need to know in my
application but someone might...
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/patch/?9555>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/