All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paavo Leinonen <paavo.leinonen@tieto.com>
To: ofono@ofono.org
Subject: Re: Selecting multiple radio access technologies in oFono
Date: Wed, 02 Feb 2011 11:33:11 +0200	[thread overview]
Message-ID: <4D4924D7.4060406@tieto.com> (raw)
In-Reply-To: <1296591930.2619.60.camel@tucson>

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

Hi Aki,

On 02/01/2011 10:25 PM, Aki Niemi wrote:
> The current API has 'gsm', 'umts', 'lte' and 'any'. I think you are
> suggesting something like 'all-but-lte', right?
I think it would be nice if user could be able to select multiple
preferred  bands, not just only one. The use case I came up with was
this 'all-but-lte'.
>> Other approach could be that we would rephrase existing API so that
>> instead of
>> using "only" LTE, we would use LTE whenever available and some older
>> technology
>> when LTE coverage is lacking. So user would select "highest" allowed radio
>> access without restrictions to use only one technology which has been
>> selected.
> This is what 'any' essentially is for.
You can't limit preferred bands with 'any'. I was trying to find an
alternative for polluting API by listing all the possible combinations
('gsm_umts', 'gsm_lte', 'umts_lte') in API.

However, I don't think we need this anymore as Rémi kindly pointed out
a solution earlierwhich involves dictionary with strings and booleans.

Br,
Paavo

  reply	other threads:[~2011-02-02  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 13:59 Selecting multiple radio access technologies in oFono Paavo Leinonen
2011-01-31 14:08 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-02-01 20:25 ` Aki Niemi
2011-02-02  9:33   ` Paavo Leinonen [this message]
2011-02-02  9:42     ` Marcel Holtmann
2011-02-02 10:05       ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-02-02 10:31       ` Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2011-02-02 10:44         ` Marcel Holtmann
2011-02-02 12:00           ` Kjetil ASDAL
2011-02-02 12:46             ` Lucas De Marchi
2011-02-02 13:10               ` Kjetil ASDAL

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=4D4924D7.4060406@tieto.com \
    --to=paavo.leinonen@tieto.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.