From: Slava Monich <slava.monich@jolla.com>
To: ofono@ofono.org
Subject: Re: RFC: Ubuntu Touch, MMS, and Provisioning
Date: Wed, 05 Mar 2014 11:39:13 +0200 [thread overview]
Message-ID: <5316F0C1.60501@jolla.com> (raw)
In-Reply-To: <5316965A.5070902@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
>> 3. No way to associate additional APN properties with a gprs_context.
>>
>> apns-conf.xml has many additional APN attributes which don't map
>> directly to gprs_context properties ( eg. authtype, mvno_type, ... ).
>>
>
> If you have usecases in mind for some of these properties, feel free
> to suggest extensions to the oFono API.
>
What do you think about extending org.ofono.ConnectionContext API with
Add/RemoveProperty calls and PropertyAdded/Removed signals to allow
platform/application specific properties of type string? Use cases
include marking connections as preferred/default or assigning priorities
to them, tracking the origin of the context (OTA, local provision or
manually edited) and who knows what else.
Regards,
-Slava
next prev parent reply other threads:[~2014-03-05 9:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 0:06 RFC: Ubuntu Touch, MMS, and Provisioning Tony Espy
2014-03-05 3:13 ` Denis Kenzior
2014-03-05 9:39 ` Slava Monich [this message]
2014-03-05 16:32 ` Denis Kenzior
2014-03-05 17:37 ` Slava Monich
2014-03-05 17:52 ` Denis Kenzior
2014-03-05 18:29 ` Marcel Holtmann
2014-03-05 21:15 ` Slava Monich
2014-03-05 22:01 ` Denis Kenzior
2014-03-05 23:36 ` Slava Monich
2014-03-06 1:15 ` Tony Espy
2014-03-06 3:04 ` Marcel Holtmann
2014-03-06 0:03 ` Tony Espy
2014-03-06 5:54 ` Denis Kenzior
2014-03-07 4:38 ` Tony Espy
2014-03-07 5:40 ` Denis Kenzior
2014-03-08 0:23 ` Tony Espy
2014-03-08 3:37 ` Denis Kenzior
2014-03-05 17:57 ` Marcel Holtmann
2014-03-05 23:42 ` Tony Espy
2014-03-06 2:41 ` Marcel Holtmann
2014-03-08 0:30 ` Tony Espy
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=5316F0C1.60501@jolla.com \
--to=slava.monich@jolla.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.