On Tue, Jul 10, 2012 at 4:55 AM, Patrick Oppenlander <pattyo.li...@gmail.com > wrote:
> On 05/07/12 20:19, Ajay Garg wrote: > > Hi all. > > I ran into a issue, as described at > https://bugs.freedesktop.org/show_bug.cgi?id=51501 > > > This behaviour is not a bug. It's a side-effect of how MDNS is > (intentionally) designed. > > Your bug report states that the callback is not called. It will in fact be > called, it just takes a long time. > Yes, I think it would. But the callback is not called after 120 seconds. May be after 75 minutes.. but I haven't waited that long enough :) Also, as per https://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns-15#section-10, the standard says that the timeout is expected to be 120 seconds. So, at least making #define AVAHI_DEFAULT_TTL_HOST_NAME #define AVAHI_DEFAULT_TTL configurable (and not hard-coded), would make it more convenient for personal customizations. Just my 2 cents :) Thanks and Regards, Ajay > > > > I followed these steps :: > > a) > I changed the values to > > #define AVAHI_DEFAULT_TTL_HOST_NAME (20) > #define > AVAHI_DEFAULT_TTL (20) > > > This is a pretty bad idea as these records will need to be refreshed at 17 > second intervals. > > Some people already consider mDNS to be a "chatty" protocol [1]. This kind > of thing just exacerbates the problem. > > Patrick > > [1] http://www.net.princeton.edu/filters/mdns.html > > _______________________________________________ > avahi mailing list > avahi@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/avahi > >
_______________________________________________ avahi mailing list avahi@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/avahi
