Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Using ASCII based files for link key storage
Date: Sat, 16 Apr 2005 20:33:48 +0200	[thread overview]
Message-ID: <1113676428.16433.80.camel@pegasus> (raw)
In-Reply-To: <200504162001.57955.bluez-devel@schaettgen.de>

Hi Fred,

> > > So first the new place for runtime things like link keys, names etc. I
> > > decided to use "/var/cache/bluetooth/<bdaddr>/" as the base directory
> > > and then use the file "linkkeys" for the actual link keys. And we will
> > > use "names" for the device name cache. The "bdaddr" is the address of
> > > the local adapter.
> >
> > According to the file hierarchy standard, /var/cache is for files which
> > "can be deleted without data loss". For cached device names it's probably
> > fine. They can't be recomputed if a device isn't in reach, but if it is,
> > the device name can be fetched again automatically. But I'm not if this
> > should include link keys. They can't be regenerated automatically without
> > bothering the user. Deleting them might even break at setup, where the peer
> > device isn't reachable easiliy after initial setup. Maybe /var/lib..? I'm
> > not really an expert in this area.
> 
> After thinking about it a little longer, I would even put the device name 
> cache under /var/lib/bluetooth. /var/cache is intended for files with the 
> purpose to reduce the load on any kind of resource, be it cpu, memory or 
> network. But that's not why bluez is caching device names. It's because we 
> want a reliable offline lookup capability. Caches should be completely 
> transparent, but this wouldn't be the case here. If the cache is gone, then 
> applications could not display a user friendly name, no matter how hard they 
> try. It's the same difference as the difference between a browser cache and a 
> proxy for offline browsing.

I am fine with it to put it under the /var/lib/bluetooth/ directory. The
code in the CVS has been changed now.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-04-16 18:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16 16:23 [Bluez-devel] Using ASCII based files for link key storage Marcel Holtmann
2005-04-16 17:32 ` Fred Schaettgen
2005-04-16 18:01   ` Fred Schaettgen
2005-04-16 18:33     ` Marcel Holtmann [this message]
2005-04-18 11:35       ` Marcel Holtmann
2005-04-16 19:04   ` Marcel Holtmann
2005-04-16 21:21     ` Fred Schaettgen
2005-04-16 21:38       ` Marcel Holtmann
2005-04-16 23:16 ` Marcel Holtmann
2005-04-17 18:41   ` Guylhem Aznar
2005-04-17 18:54     ` 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=1113676428.16433.80.camel@pegasus \
    --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