From: Suraj Sumangala <suraj@Atheros.com>
To: <linux-bluetooth@vger.kernel.org>,
<Jothikumar.Mothilal@Atheros.com>,
<joakim.xj.ceder@stericsson.com>, <claudio.takahasi@gmail.com>,
<Waldemar.Rymarkiewicz@tieto.com>, <Arkadiusz.Lichwa@tieto.com>
Subject: Re: [RFC] Sim Access Profile API doc
Date: Tue, 7 Sep 2010 18:24:18 +0530 [thread overview]
Message-ID: <4C8635FA.5010108@Atheros.com> (raw)
In-Reply-To: <20100907101230.GA6309@jh-x301>
Hi Johan,
On 9/7/2010 3:42 PM, Johan Hedberg wrote:
> We're defining an API here, not implementation specific details, so I
> don't quite understand your concern. What's the point of defining an
> agent object if it will not receive any method calls? The RegisterAgent
> might as well be called EnableServer in that case and not contain any
> object path parameter at all.
>
> Having a proper agent interface and methods in it corresponding to SAP
> commands makes much more sense imho than emiting signals for SAP
> commands and receiving method calls for the SAP replies. It also doesn't
> in any way restrict the agent side implementation details. A D-Bus
> method call-method reply pair is a more intuitive mapping to a
> SAP-command-SAP-response pair compared to a D-Bus signal + method call
> which don't have any tight API level association (anybody can catch the
> signal and anybody can send the method call).
>
Got your point, Thanks.
Also, do let me know if you have any other suggestion regarding the
interface.
Regards
Suraj
prev parent reply other threads:[~2010-09-07 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 6:02 [RFC] Sim Access Profile API doc Suraj Sumangala
2010-09-07 7:47 ` Uwe Kleine-König
2010-09-07 8:36 ` Waldemar.Rymarkiewicz
2010-09-07 9:28 ` Suraj Sumangala
2010-09-07 12:24 ` Waldemar.Rymarkiewicz
2010-09-07 9:29 ` Johan Hedberg
2010-09-07 9:58 ` Suraj Sumangala
2010-09-07 10:12 ` Johan Hedberg
2010-09-07 12:54 ` Suraj Sumangala [this message]
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=4C8635FA.5010108@Atheros.com \
--to=suraj@atheros.com \
--cc=Arkadiusz.Lichwa@tieto.com \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=Waldemar.Rymarkiewicz@tieto.com \
--cc=claudio.takahasi@gmail.com \
--cc=joakim.xj.ceder@stericsson.com \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).