From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Cached friendly names never updated when changed
Date: Wed, 26 Mar 2008 18:05:42 +0100 [thread overview]
Message-ID: <39C940F5-0157-43EB-9841-D5B7D35CCBF9@holtmann.org> (raw)
In-Reply-To: <47EA8056.8090500@idlum.be>
Hi Pierre-Yves,
> It seems that once a friendly name has been cached to /var/lib/
> bluetooth/*/names, RemoteNameUpdated signals contain this cached
> name forever, and user is never informed of a name change unless
> those "names" files are deleted.
the names are never updated once retrieved. At least not via an
inquiry run. If you connect to a remote device, it will update the
name. Another option is Extended Inquiry support if you have the
hardware for it.
The reason behind this is that the remote name operation is too
expensive if you don't have an ACL link between two devices. And a lot
of times the name doesn't change so often or it is unimportant anyway.
Regards
Marcel
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-03-26 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 16:56 [Bluez-devel] Cached friendly names never updated when changed Pierre-Yves Paulus
2008-03-26 17:05 ` Marcel Holtmann [this message]
2008-03-27 13:11 ` Pierre-Yves Paulus
2008-03-27 15:06 ` Marcel Holtmann
2008-03-27 15:24 ` Pierre-Yves Paulus
2008-03-27 15:45 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39C940F5-0157-43EB-9841-D5B7D35CCBF9@holtmann.org \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox