Open Source Telephony
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH] Cache EF-PNN, EF-OPL sim files on disk.
Date: Sat, 18 Jul 2009 13:39:06 +0200	[thread overview]
Message-ID: <1247917146.4549.80.camel@violet> (raw)
In-Reply-To: <fb249edb0907180432x4a44eafcu8f1ed47914cfae35@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]

Hi Andrzej,

> > However, not all files can be updated by the user.  Namely files with the 'ADM'
> > for UPDATE access condition.  The only way they can be changed is at a service
> > center.
> >
> > What do you think of transparently caching only such files?  This would include
> > the ones we're really interested in caching anyway, namely EFspn, EFpnn,
> > EFopl, EFust, etc.
> 
> True, I was going to add code or a TODO in ofono_sim_write() to
> invalidate cache but it's a good point about updating outside ofono
> control.  I now added a parameter to ofono_sim_read() to indicate that
> a file can be cached on disk, making it a little less transparent.  In
> previous version I had separate entry points for cached read.
> 
> >
> > If we decide to do this, we should store them in /var/lib/ instead of
> > /var/cache, since these files will be stored semi-permanently.
> 
> Ok, changed.  There's also a standard path /var/state, I don't know if
> it's better or worse.

go with /var/lib since that is most common for persistent information.
You can use /var/cache for information that can be easily retrieved
again without having an impact on the functionality.

The /var/state should not be bothered with. If you have information that
are only stored for one session then /var/run should be used. However
that will be wiped during reboot.

Regards

Marcel



  reply	other threads:[~2009-07-18 11:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05  3:14 [PATCH] Cache EF-PNN, EF-OPL sim files on disk Andrzej Zaborowski
2009-07-14 20:54 ` Denis Kenzior
2009-07-18  4:34   ` Andrzej Zaborowski
2009-07-18  6:02     ` Denis Kenzior
2009-07-18 11:32       ` andrzej zaborowski
2009-07-18 11:39         ` Marcel Holtmann [this message]
2009-07-18 12:42         ` andrzej zaborowski
2009-07-20 16:12           ` Andrzej Zaborowski
2009-07-20 14:24             ` Marcel Holtmann
2009-07-20 14:56               ` andrzej zaborowski
2009-07-27 23:13             ` Denis Kenzior
2009-07-28  1:39               ` Andrzej Zaborowski
2009-07-29 22:24                 ` Denis Kenzior

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=1247917146.4549.80.camel@violet \
    --to=marcel@holtmann.org \
    --cc=ofono@ofono.org \
    /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