From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] Cache EF-PNN, EF-OPL sim files on disk.
Date: Sat, 18 Jul 2009 01:02:26 -0500 [thread overview]
Message-ID: <200907180102.27090.denkenz@gmail.com> (raw)
In-Reply-To: <1247891688-10028-1-git-send-email-andrew.zaborowski@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
Hi,
> This uses plain files in /var/cache/ofono for storing contents of the
> operator lists to avoid possibly numerous queries to the SIM on every
> startup. Files are indexed with IMSI. I'm not 100% sure about the
> autoconf magic.
>
> Users need to rerun bootstrap-configure after applying this.
>
> File format slightly changed in this second version (make it as simple as
> possible).
> return -1;
I somewhat like the idea of transparently caching the SIM file system,
unfortunately we can't do it for all files. Suppose a user shuts off oFono
device, takes out the SIM and puts it in another device. Then modifies some
settings (e.g. like MBDN or MSISDN.) Then the SIM is returned to oFono based
device.
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.
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. If really
necessary, the carrier service center could probably remove the cache somehow
during the SIM upgrade.
Regards,
-Denis
next prev parent reply other threads:[~2009-07-18 6:02 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 [this message]
2009-07-18 11:32 ` andrzej zaborowski
2009-07-18 11:39 ` Marcel Holtmann
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=200907180102.27090.denkenz@gmail.com \
--to=denkenz@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.