All of lore.kernel.org
 help / color / mirror / Atom feed
From: Slava Monich <slava.monich@jolla.com>
To: ofono@ofono.org
Subject: Re: [PATCH] gprs: Use "internet" apn for auto-created context
Date: Sun, 19 Jan 2014 12:25:53 +0200	[thread overview]
Message-ID: <52DBA831.20000@jolla.com> (raw)
In-Reply-To: <52D8A6EB.90506@gmail.com>

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

Hi Denis,

> Hi Slava,
>
> A gentle reminder to please not top-post on this mailing list.
>
> On 01/16/2014 02:52 PM, Slava Monich wrote:
>> Hi Denis,
>>
>> Sorry to bother you, but I don't quite get the logic. There's something
>> that needs to be done in case if ALL provisioning plugins have run and
>> failed. How could that be a part of a provisioning plugin? They all have
>> already run and failed by definition of the problem.
>
> We do; we create an empty context to signify that provisioning has 
> failed.  I do realize you mean well, but you're trying to wildly guess 
> (at least that is how I read the commit description) and breaking 
> existing behavior.
>

How can you tell an empty context created by a provisioning plugin from 
an empty context created by gprs.c after all provisioning plugins have 
failed? Or from the access point edited by the user in such a way that 
it looks exactly like the empty context created in gprs.c? You can't. 
They are all identical. Empty context is not a reliable indication of a 
provisioning failure.

A better, unambiguous indication would be to not create any contexts at 
all. Actually, I was assuming that it was the case and was quite 
surprised to find out that it was ofono creating the default context.

It's surely not breaking anything for Jolla. It would only improve 
chances of GPRS access to work out of the box. But of course in theory 
it may break something on some other platform. Any change, even an 
obvious bug fix can break existing behavior.

Finally, about 15% of all GPRS Internet access points in the world are 
called "internet" and have no user name or password. It's by far the 
most common use case. So it's not a wild guess at all. It's real life 
experience.

Regards,
-Slava

  reply	other threads:[~2014-01-19 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 14:43 [PATCH] gprs: Use "internet" apn for auto-created context Slava Monich
2014-01-16 17:04 ` Denis Kenzior
2014-01-16 20:52   ` Slava Monich
2014-01-17  3:43     ` Denis Kenzior
2014-01-19 10:25       ` Slava Monich [this message]
2014-01-20  3:12         ` 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=52DBA831.20000@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.