From: Jukka Saunamaki <jukka.saunamaki@nokia.com>
To: ofono@ofono.org
Subject: Re: [RFC PATCHv2 1/4] Automatic provisioning of GPRS context settings
Date: Mon, 03 Jan 2011 12:44:19 +0200 [thread overview]
Message-ID: <1294051459.2077.22.camel@jsaunama-desktop> (raw)
In-Reply-To: <87lj32xt30.fsf@potku.valot.fi>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Hello
On Mon, 2011-01-03 at 10:57 +0200, Kalle Valo wrote:
> Jukka Saunamaki <jukka.saunamaki@nokia.com> writes:
> > Settings database is an XML formatted file (combination of all
> > xml-files in a directory), containing one element per settings for a
> > specific type of GPRS context (internet, mms)
>
> > Example:
> > <?xml version="1.0"?>
> > <settings>
> > <access type="internet" mcc="246" mnc="81" spn="oFono" name="Phonesim Internet-GPRS" apn="internet.apn"/>
> > <access type="mms" mcc="246" mnc="81" spn="oFono" name="Phonesim MMS-GPRS" apn="mms.apn" protocol="ipv4" username="mmsuser" password="mmspass" proxy="10.11.12.13:8080" mmsserver="http://mms.example.com:8000"/>
> > </settings>
>
> The format here doesn't look very extensible to me, more like csv with
> steroids and not proper xml. Any particular reason why you can't use the
> same format as in mobile-broadband-provider-info?
>
> http://git.gnome.org/browse/mobile-broadband-provider-info/tree/serviceproviders.xml
Well, my intention was to make format simple and fast to parse, but
still be extensible enough, which I think my proposed format fulfills.
These <access>-elements contain just data needed for GPRS context
settings (as attributes), and if there is need for any other operator
specific provisioning information, you can always add separate elements,
this is still proper XML.
--Jukka
next prev parent reply other threads:[~2011-01-03 10:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 7:31 [RFC PATCHv2 1/4] Automatic provisioning of GPRS context settings Jukka Saunamaki
2011-01-03 7:31 ` [RFC PATCHv2 1/4] sim: add ofono_sim_get_mnc_length Jukka Saunamaki
2011-01-03 20:37 ` Marcel Holtmann
2011-01-03 7:31 ` [RFC PATCHv2 2/4] operator-settings: Add GPRS context provisioning sources Jukka Saunamaki
2011-01-03 7:31 ` [RFC PATCHv2 3/4] gprs: add automatic context settings provisioning Jukka Saunamaki
2011-01-03 7:31 ` [RFC PATCHv2 4/4] operator-settings: Example GPRS context settings file Jukka Saunamaki
2011-01-03 8:57 ` [RFC PATCHv2 1/4] Automatic provisioning of GPRS context settings Kalle Valo
2011-01-03 10:44 ` Jukka Saunamaki [this message]
2011-01-03 11:40 ` Kalle Valo
2011-01-03 13:32 ` Aki Niemi
2011-01-03 13:38 ` Jukka Saunamaki
2011-01-03 20:34 ` Marcel Holtmann
2011-01-03 11:28 ` Aki Niemi
2011-01-03 20:31 ` Marcel Holtmann
2011-01-03 23:03 ` Marcel Holtmann
2011-01-04 7:13 ` Jukka Saunamaki
2011-01-04 8:05 ` Marcel Holtmann
2011-01-04 8:42 ` Jukka Saunamaki
2011-01-04 9:29 ` Marcel Holtmann
2011-01-04 8:23 ` Kalle Valo
2011-01-04 8:30 ` Marcel Holtmann
2011-01-04 10:00 ` Kalle Valo
2011-01-11 0:59 ` Marcel Holtmann
2011-01-13 22:41 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2011-09-08 7:38 manju krishna
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=1294051459.2077.22.camel@jsaunama-desktop \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox