All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jukka Saunamaki <jukka.saunamaki@nokia.com>
To: ofono@ofono.org
Subject: Re: [RFC PATCH 0/4] Automatic provisioning of GPRS context settings
Date: Wed, 22 Dec 2010 12:08:11 +0200	[thread overview]
Message-ID: <4D11CE0B.2040402@nokia.com> (raw)
In-Reply-To: <1292940661.2658.23.camel@aeonflux>

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

Hi

On 21/12/10 16:11, ext Marcel Holtmann wrote:
>> Settings database is CSV (comma separated values) formatted file(s)
>> with fields for: (type=INTERNET|MMS protocol=ipv4|ipv6)
>> MCC,MNC,SPN,type,UI name, APN, username, password, protocol, proxy IP address, proxy port, MMS server URL
>>
>> e.g. file /etc/ofono/operator-settings/50-default.csv:
>> 001,01,test,INTERNET,Network Tester GPRS,internet,,,,,,
>> 246,81,oFono,INTERNET,Phonesim Internet,internet.apn,,,ipv4,,,
>> 246,81,oFono,MMS,Phonesim MMS,mms.apn,mmsuser,mmspass,ipv4,10.10.10.10,8080,http://192.168.0.111:8002
>>
>> This format is loosely based on what was used in Nokia N900 for
>> similar use.
> I am really not set on a file format, but my obvious question is if we
> don't wanna better use keyfile or XML based database since that are the
> file formats we are currently using inside oFono. We have not used CSV
> at all so far.
>
> My vote would go for keyfile or XML since it is a bit more self
> explanatory with its fields. And the order of values doesn't really
> matter.
>
> The one thing that I don't like about CSV is that you have no real
> flexibility with its format. Especially coming think about that we might
> have to extend this additional information for IMS or operator specific
> behavior.

Good points. I suggested csv, because it is very simple and fast to 
parse, and it has proven to be "good enough" for this specific purpose. 
But, true, it is also very inflexible.
So, how about something like this XML format: (better element name 
suggestions welcome)

<?xml version="1.0"?>
<settings>
<access type="internet" mcc="001" mnc="01" spn="test" name="Example 
Internet GPRS" apn="internet" protocol="ipv4"/>
<access type="mms" mcc="001" mnc="01" spn="test" name="Example MMS GPRS" 
apn="mms" proxy="10.11.12.13:8080" mmsserver="http://mms.example.com:8000"/>
<access ... />
...
</settings>

This would still be quite easy and fast to parse (using glib simple XML 
parser), would not be hugely larger in size and would allow easy adding 
of new attributes/values.

Also, do you or anybody have comments about the logic of provisioning, 
and changes to sim and gprs parts?

--Jukka Saunamäki


      reply	other threads:[~2010-12-22 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21  9:01 [RFC PATCH 0/4] Automatic provisioning of GPRS context settings Jukka Saunamaki
2010-12-21  9:01 ` [RFC PATCH 1/4] operator-settings: Add GPRS context provisioning sources Jukka Saunamaki
2010-12-21  9:01 ` [RFC PATCH 2/4] sim: add ofono_sim_get_mnc_length Jukka Saunamaki
2010-12-21  9:01 ` [RFC PATCH 3/4] gprs: add automatic context settings provisioning Jukka Saunamaki
2010-12-21  9:01 ` [RFC PATCH 4/4] operator-settings: Example GPRS context settings file Jukka Saunamaki
2010-12-21 14:11 ` [RFC PATCH 0/4] Automatic provisioning of GPRS context settings Marcel Holtmann
2010-12-22 10:08   ` Jukka Saunamaki [this message]

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=4D11CE0B.2040402@nokia.com \
    --to=jukka.saunamaki@nokia.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.