From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 0/2] Add ResetProperties method to ConnectionContext interface
Date: Fri, 20 Feb 2015 10:00:31 -0600 [thread overview]
Message-ID: <54E75A1F.8070709@gmail.com> (raw)
In-Reply-To: <1424347193-6828-1-git-send-email-tommi.kenakkala@tieto.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Hi Tommi,
On 02/19/2015 05:59 AM, Tommi Kenakkala wrote:
> In some cases it is useful to reset connection context settings back to ones
> ofono provisioning resolved initially.
> What's your opinion on the API design, implementation and use-case described
> next?
>
Why don't you just remove the settings file and restart oFono?
> Deactivation of the context is obviously mandatory. The reasoning for placing
> this into ofono is handling client requests consistently and avoiding race
> conditions. Using this approach ofono does not re-activate the context, that's
> done by ConnMan or whatever connection manger the system uses.
>
I'm not so sure that this is a good idea. A 'live' reset of the
settings just seems wrong to me. Why would you ever want to do that
anyway? If something is working, why bother resetting the settings?
oFono supports arbitrary number of contexts, so your UI can always add
more. So if you need to re-provision, let your UI handle this. The UI
should be capable of reading the provisioning database anyway in order
to handle duplicates, etc.
Regards,
-Denis
next prev parent reply other threads:[~2015-02-20 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 11:59 [PATCH 0/2] Add ResetProperties method to ConnectionContext interface Tommi Kenakkala
2015-02-19 11:59 ` [PATCH 1/2] gprs: " Tommi Kenakkala
2015-02-19 11:59 ` [PATCH 2/2] doc: Document ResetProperties method Tommi Kenakkala
2015-02-20 16:00 ` Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-23 12:31 Re: [PATCH 0/2] Add ResetProperties method to ConnectionContext interface Tommi Kenakkala
2015-02-23 15:47 ` 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=54E75A1F.8070709@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 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.