Open Source Telephony
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [RFC PATCHv2 1/4] Automatic provisioning of GPRS context settings
Date: Tue, 04 Jan 2011 00:30:52 -0800	[thread overview]
Message-ID: <1294129852.5852.76.camel@aeonflux> (raw)
In-Reply-To: <87k4ilnkkq.fsf@potku.valot.fi>

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

Hi Kalle,

> > thinking about this a bit more and with the background that there is
> > already an existing public database, we might should just enable a
> > provision driver inside the oFono core.
> >
> > Meaning that we can have multiple implementations of different databases
> > with just different priorities. Each nicely separated in their own
> > plugin and we don't bother the oFono core with where to get the data
> > from. So my idea would be that the oFono core just asks to provision a
> > new context. If a plugin feels responsible, then it does so. If not then
> > it stays empty.
> 
> I like the idea. Simple to implement and we get maximum extensibility.
> 
> Are you willing to take a plugin into ofono git which would use
> mobile-broadband-provider-info database? Or should people maintain the plugins
> out of tree?

in general I would accept any of such plugins into the tree. However we
need to be a bit careful with the priority. And of course they need to
have some sort of usage.

What I expect to see in long term is that we have two or three different
formats. And they just differ because of the different vertical targets.

> For me the best would be to have all plugins in ofono tree and
> enable/disable them with configure switches.

I wanna use priorities and smart detection to use them. Nothing for the
user to configure. Just installing some extra packages should active its
usage. And yes, I want to make it possible to build all plugins at all
time.

Regards

Marcel



  reply	other threads:[~2011-01-04  8:30 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
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 [this message]
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=1294129852.5852.76.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox