From: Marcel Holtmann <marcel@holtmann.org>
To: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>
Cc: linux-bluetooth@vger.kernel.org, suraj@atheros.com,
Johan Hedberg <johan.hedberg@gmail.com>,
joakim.xj.ceder@stericsson.com
Subject: Re: [PATCH 1/4] Sim Access Profile API
Date: Wed, 10 Nov 2010 14:33:10 +0900 [thread overview]
Message-ID: <1289367190.9615.235.camel@aeonflux> (raw)
In-Reply-To: <1288791271-13857-2-git-send-email-waldemar.rymarkiewicz@tieto.com>
Hi Waldemar,
> New API for Sim Access Profile.
> ---
> Makefile.am | 2 +-
> doc/sap-api.txt | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 58 insertions(+), 1 deletions(-)
> create mode 100644 doc/sap-api.txt
>
> diff --git a/Makefile.am b/Makefile.am
> index 873f2df..e1183de 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -352,7 +352,7 @@ EXTRA_DIST += doc/manager-api.txt \
> doc/service-api.txt doc/agent-api.txt doc/attribute-api.txt \
> doc/serial-api.txt doc/network-api.txt \
> doc/input-api.txt doc/audio-api.txt doc/control-api.txt \
> - doc/hfp-api.txt doc/assigned-numbers.txt
> + doc/hfp-api.txt doc/assigned-numbers.txt doc/sap-api.txt
>
> AM_YFLAGS = -d
>
> diff --git a/doc/sap-api.txt b/doc/sap-api.txt
> new file mode 100644
> index 0000000..7951f56
> --- /dev/null
> +++ b/doc/sap-api.txt
> @@ -0,0 +1,57 @@
> +BlueZ D-Bus Sim Access Profile API description
> +***********************************
> +
> +Copyright (C) 2010 ST-Ericsson SA
> +
> +
> +Sim Access Profile hierarchy
> +============================
> +
> +Service org.bluez
> +Interface org.bluez.SimAccess
> +Object path [variable prefix]/{hci0,hci1,...}
> +
> +Methods void Enable()
> +
> + Start up SAP server and register SDP record for it.
> +
> + Possible errors: org.bluez.Error.Failed
> +
> + void Disable()
> +
> + Shudown SAP server and remove the SDP record.
> +
> + Possible errors: org.bluez.Error.Failed
I don't like this. If you have properties then just changing the
property should be enough. So a SetProperty is more appropriate.
> +
> + void Disconnect(boolean type)
> +
> + Disconnect SAP client from the server. The 'type'
> + parameter indicates disconnection type.
> +
> + True - gracefull disconnection
> + False - immediate disconnection
> +
> + Possible errors: org.bluez.Error.Failed
I don't like this style of method names at all. Using method names like
GracefulDisconnect and ImmediateDisconnect would be better.
However I am not sure we should differentiate here at all. We should
always to the graceful disconnect. What will the immediate disconnect
bring us?
Regards
Marcel
next prev parent reply other threads:[~2010-11-10 5:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 13:34 [PATCH 0/4] Sim Access Profile Waldemar Rymarkiewicz
2010-11-03 13:34 ` [PATCH 1/4] Sim Access Profile API Waldemar Rymarkiewicz
2010-11-10 5:33 ` Marcel Holtmann [this message]
2010-11-10 11:12 ` Waldemar.Rymarkiewicz
2010-11-10 16:07 ` Gustavo F. Padovan
2010-11-10 21:46 ` Luiz Augusto von Dentz
2010-11-15 17:29 ` Waldemar.Rymarkiewicz
2010-11-03 13:34 ` [PATCH 2/4] Sim Access Profile Manager Waldemar Rymarkiewicz
2010-11-05 9:30 ` Johan Hedberg
2010-11-05 13:31 ` Waldemar.Rymarkiewicz
2010-11-03 13:34 ` [PATCH 3/4] Sim Access Profile Server Waldemar Rymarkiewicz
2010-11-05 10:05 ` Johan Hedberg
2010-11-05 15:12 ` Waldemar.Rymarkiewicz
2010-11-03 13:34 ` [PATCH 4/4] Sim Access Profile dummy driver Waldemar Rymarkiewicz
2010-11-05 10:16 ` Johan Hedberg
2010-11-05 15:14 ` Waldemar.Rymarkiewicz
-- strict thread matches above, loose matches on Subject: below --
2010-12-02 14:14 [PATCH 1/4] Sim Access Profile API Waldemar Rymarkiewicz
2010-12-02 15:19 ` Gustavo F. Padovan
2010-12-02 15:23 ` Waldemar.Rymarkiewicz
2010-12-14 15:16 ` Waldemar.Rymarkiewicz
2010-10-20 12:11 Waldemar Rymarkiewicz
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=1289367190.9615.235.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=joakim.xj.ceder@stericsson.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=suraj@atheros.com \
--cc=waldemar.rymarkiewicz@tieto.com \
/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.