[avahi] publish-update problem

Trent Lloyd lathiat at bur.st
Sun Apr 20 00:23:17 PDT 2008


On 20/04/2008, at 11:05 AM, Lennart Poettering wrote:

> On Fri, 18.04.08 07:17, Trent Lloyd (lathiat at bur.st) wrote:
>>> What seems to happening is that when the browser registers for a  
>>> service
>>> it gets the value from the cache and then the multicast_lookup is
>>> destroyed before the next update of the record. Are there some flag
>>> settings that can be set to prevent this? I can see the cache_update
>>> function being called but the avahi_multicast_lookup_engine_notify  
>>> does
>>> nothing since the lookup msg has been removed. Though looking at  
>>> the code
>>> again subscribers are only notified of CNAME changes, so maybe I am
>>> looking in the wrong place.
>> Currently a Browser does not respond to TXT updates if you want TXT  
>> updates
>> you must keep a running Resolver
> Currently? Not just "currently". This is very unlikely to change since
> the whole distinction between "resolving" and "browsing" is because we
> want to make sure that we don't need to send around all the
> (potentially huge) meta information about each service that
> might be stored in the TXT data when a client just wants to get a
> simple list of services that are available.

Sorry that "Currently" was not actually meant to imply it would  
change, it was more a figure of speech.

> So, in short: that browsers don't know about TXT data changes is a
> feature, not a bug. For the sake of minimizing traffic.



More information about the avahi mailing list