Thanks Patrick for the reply.<br><br><br><div class="gmail_quote">On Tue, Jul 10, 2012 at 11:38 AM, Patrick Oppenlander <span dir="ltr"><<a href="mailto:pattyo.lists@gmail.com" target="_blank">pattyo.lists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="im">
<div><br>
</div>
<blockquote type="cite"><br>
<br>
<div class="gmail_quote">On Tue, Jul 10, 2012 at 4:55 AM, Patrick
Oppenlander <span dir="ltr"><<a href="mailto:pattyo.lists@gmail.com" target="_blank">pattyo.lists@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div>On 05/07/12 20:19, Ajay Garg wrote:<br>
</div>
<blockquote type="cite">Hi all.<br>
<br>
I ran into a issue, as described at <a href="https://bugs.freedesktop.org/show_bug.cgi?id=51501" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=51501</a><br>
</blockquote>
<br>
</div>
This behaviour is not a bug. It's a side-effect of how MDNS
is (intentionally) designed.<br>
<br>
Your bug report states that the callback is not called. It
will in fact be called, it just takes a long time.</div>
</blockquote>
<div><br>
<br>
Yes, I think it would.<br>
But the callback is not called after 120 seconds. May be after
75 minutes.. but I haven't waited that long enough :)<br>
<br>
Also, as per <a href="https://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns-15#section-10" target="_blank">https://tools.ietf.org/html/draft-cheshire-dnsext-multicastdns-15#section-10</a>,
the standard says that the timeout is expected to be 120
seconds.<br>
</div>
</div>
</blockquote>
<br></div>
I think you're misunderstanding how the TTLs are used. the 120
seconds refers to host specific records -- i.e. records that are
available after a resolve. A client application is not notified when
these records expire as they are transient.<br>
<br>
The 75 minute TTL is for everything else, including PTR records,
which is what you are interested in.<br>
<br>
I've never used Telepathy so I can't really offer suggestions on how
to proceed with your issue, but keep in mind that DNS-SD was never
designed to provide an iron-clad guarantee that a service is
available. The only way to determine that a service is genuinely
available is to first resolve it, and if the resolve succeeds
attempt to connect.<span class="HOEnZb"><font color="#888888"><br></font></span></div></blockquote><div><br><br>Yes, that's right. <br><br>But the use-case we need to handle (getting to know when a client has disconnected from the telepathy-salut network) wouldn't be solved by this. Therein, we need to have a mechanism by which the dis-connectivity may be known. Unfortunately, polling (or pseudo-polling) is the only ultimate way (since the going-disconnected-buddy doesn't give the "goodbye" signal, since no network-medium is available).<br>
<br><br>So, perhaps a client notification *should* get notified, once the transient-resolved-records expire??!!<br><br><br><br>Just my 2 cents :)<br><br><br><br>Thanks and Regards,<br>Ajay<br><br><br><br><br><br><br></div>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class="HOEnZb"><font color="#888888">
<br>
Patrick<br>
<br>
</font></span></div>
<br>_______________________________________________<br>
avahi mailing list<br>
<a href="mailto:avahi@lists.freedesktop.org">avahi@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/avahi" target="_blank">http://lists.freedesktop.org/mailman/listinfo/avahi</a><br>
<br></blockquote></div><br>