From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH] TODO: SMS Validity Period
Date: Wed, 02 Feb 2011 07:52:24 +0100 [thread overview]
Message-ID: <1296629544.1520.296.camel@aeonflux> (raw)
In-Reply-To: <1296591582.2619.54.camel@tucson>
[-- Attachment #1: Type: text/plain, Size: 2635 bytes --]
Hi Aki,
> > > > How does a normal user actually know what this means for him and the
> > > > network he is using? Is the network actually honoring these values at
> > > > all these days?
> > >
> > > These are not clear to me either, so I don't see the point in exposing
> > > this setting over the D-Bus interface. I would, however, err on the
> > > side of flexibility here, and make this a configuration option in
> > > main.conf (once that support is available in oFono).
> >
> > we did talk a bit about expected operator defaults especially in the
> > context of default character set etc. I think Portugal is such an
> > exception where you have to start out with a proper character set if
> > your SIM card is originated from there.
> >
> > Maybe this is another one case where just picking a proper operator
> > default is better than actually providing any option to change it.
>
> Yes, some of these language variants are mandated by certain regulators,
> some by operators. So certainly the default SMS alphabet should be a
> main.conf item.
I don't think that main.conf is really what you want here. If I
understand this requirement correctly, then the defaults have to be
picked based on the SIM card you put into the device. You don't really
wanna build country or operator specific main.conf and ship different
software core software to every single operator.
So I think we need to approach this a little bit different to make it
easy to handle and also easy to update if needed while still having the
same distribution running on every device no matter what country it
actually got manufactured for. And with GSM we are in the lucky position
that every single SIM card has its MCC and MNC. My idea is that we go
with sensible operator defaults here.
My idea is to have /usr/lib/ofono/defaults/ directory where we can store
a set of proper default values with operator variants. So any builtin
default could be easily overwritten this way. An example would be to
have a sms.conf file here.
[bearer]
default=cs-preferred
262=ps-preferred
26202=ps-only
[charset]
...
This way the atom could come in and read this file for a new SIM card
and automatically set sensible defaults. And if not present we just use
the hardcoded builtin defaults.
And we can keep this minimal since there will be only so many exceptions
to the default here. The other advantage is that this can actually be
maintained outside of oFono by the device manufacturer. In the end these
might be all so trivial that we can just ship them with oFono directly.
Regards
Marcel
next prev parent reply other threads:[~2011-02-02 6:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 9:01 [PATCH] TODO: SMS Validity Period Miia Leinonen
2011-01-31 9:47 ` Marcel Holtmann
2011-01-31 10:06 ` Miia Leinonen
2011-01-31 10:31 ` Marcel Holtmann
2011-01-31 11:23 ` Aki Niemi
2011-01-31 12:42 ` Marcel Holtmann
2011-02-01 20:19 ` Aki Niemi
2011-02-02 6:52 ` Marcel Holtmann [this message]
2011-01-31 12:27 ` Miia.Leinonen
2011-01-31 12:52 ` Marcel Holtmann
2011-01-31 14:54 ` Miia Leinonen
2011-01-31 15:44 ` Marcel Holtmann
2011-02-01 13:01 ` Miia Leinonen
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=1296629544.1520.296.camel@aeonflux \
--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 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.