From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] provision: allow duplicate apn's from mbpi
Date: Wed, 02 Jan 2019 12:36:59 -0600 [thread overview]
Message-ID: <f0ac37c3-3fcd-829d-fba2-e82d98ffaeb3@gmail.com> (raw)
In-Reply-To: <20190102115053.79191-2-martin@geanix.com>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Hi Martin,
On 01/02/2019 05:50 AM, Martin Hundebøll wrote:
> Let the user/connection-manager decide what to do with duplicate apn
> entries instead of bailing out with an error.
> ---
> plugins/provision.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
While seemingly trivial, this actually has a huge impact on user
experience. The problem is that there's no good meta-data for the user
to make the decision as to which service is the one they want.
Also, I'm not sure how this impacts connman? In theory it is supposed
to auto-activate the internet context, and if there are multiple one of
these, I'm not sure if it gets confused?
The typical guidance is that if a database contains potential
duplicates, then a UI Wizard is needed to guide the user to choose the
appropriate one and provision the context that way.
Alternatively, provide a provisioning database without conflicts,
perhaps specific to the users / operators you're targeting.
Regards,
-Denis
next prev parent reply other threads:[~2019-01-02 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 11:50 [PATCH] gprs: fix allocation of context id Martin =?unknown-8bit?q?Hundeb=C3=B8ll?=
2019-01-02 11:50 ` [PATCH] provision: allow duplicate apn's from mbpi Martin =?unknown-8bit?q?Hundeb=C3=B8ll?=
2019-01-02 18:36 ` Denis Kenzior [this message]
2019-01-04 14:03 ` Martin =?unknown-8bit?q?Hundeb=C3=B8ll?=
2019-01-04 21:03 ` Denis Kenzior
2019-01-07 8:50 ` Martin =?unknown-8bit?q?Hundeb=C3=B8ll?=
2019-01-08 17:50 ` Denis Kenzior
2019-01-02 18:20 ` [PATCH] gprs: fix allocation of context id Denis Kenzior
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=f0ac37c3-3fcd-829d-fba2-e82d98ffaeb3@gmail.com \
--to=denkenz@gmail.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