From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 3/5 v3] nettime: DBUS and compilation configuration
Date: Fri, 21 Jan 2011 14:31:14 +0100 [thread overview]
Message-ID: <1295616674.3873.308.camel@aeonflux> (raw)
In-Reply-To: <1295616529.10774.11.camel@apaila-ThinkPad-T410>
[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]
Hi Antti,
> > > > please don't implement org.ofono interface in timed. Just implement a
> > > > timed specific (com.nokia.time) interface and punch the whole for that
> > > > in the timed D-Bus policy.
> > >
> > > I think there is some disconnect here. The intention is to implement a
> > > similar agent interface as PushNotification and SmartMessaging already
> > > do, with the exception that the one and only agent is known beforehand
> > > and "hard-coded" to the plugin.
> >
> > that is not what I said and that is clearly not the intent here.
> >
> > > This is a generic interface that some other time information sink
> > > could also implement, so it makes sense to have it in the org.ofono
> > > namespace. Regardless of which namespace we use, though, it is oFono
> > > that will be calling methods on this interface, and thus it needs to
> > > have this interface opened in its D-Bus config.
> >
> > They will be always specific to the target daemon and that is fine. This
> > is not up to oFono to define and that is point here.
> >
> > > > The plugin is timed specific since it monitors com.nokia.time and thus
> > > > should also target a timed specific API. Not a generic oFono API
> > > > description.
> > >
> > > This is really just another agent API in oFono, just one with a
> > > build-time registration mechanism for agents.
> >
> > It is not. This is timed exposing an API to get notifications from a
> > cellular stack and then a timed specific plugin inside oFono. It has
> > nothing to do with an oFono defined D-Bus API.
>
> As I see, the question at the moment is where to punch the hole in D-Bus
> configuration; alternatives being either in ofono or in timed side. I
> can see the rationale and reasoning behind both approaches, but in order
> to make some progress with this matter we need a decision. So, should we
> take a vote or what? After all isn't this a non-functional,
> matter-of-taste type of question?
since it should be com.nokia.timed interface, it should be done all by
timed. The timed plugin inside oFono is just a user.
Regards
Marcel
next prev parent reply other threads:[~2011-01-21 13:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 9:49 [PATCH 0/5 v3] Network Time plugin Antti Paila
2011-01-13 9:49 ` [PATCH 1/5 v3] nettime: Header file for nettime plugins Antti Paila
2011-01-13 12:58 ` Aki Niemi
2011-01-13 9:49 ` [PATCH 2/5 v3] nettime: Network time plugin implementation Antti Paila
2011-01-13 9:49 ` [PATCH 3/5 v3] nettime: DBUS and compilation configuration Antti Paila
2011-01-14 0:22 ` Marcel Holtmann
2011-01-17 8:17 ` Antti Paila
2011-01-17 16:09 ` Marcel Holtmann
2011-01-17 17:02 ` Mika.Liljeberg
2011-01-17 18:37 ` Denis Kenzior
2011-01-18 7:36 ` Aki Niemi
2011-01-18 14:59 ` Marcel Holtmann
2011-01-19 8:10 ` Aki Niemi
2011-01-20 11:19 ` Marcel Holtmann
2011-01-21 13:28 ` Antti Paila
2011-01-21 13:31 ` Marcel Holtmann [this message]
2011-01-13 9:49 ` [PATCH 4/5 v3] nettime: Documentation Antti Paila
2011-01-13 9:49 ` [PATCH 5/5 v3] nettime: Mock Timed for testing Antti Paila
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=1295616674.3873.308.camel@aeonflux \
--to=marcel@holtmann.org \
--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