From: Johan Hedberg <johan.hedberg@gmail.com>
To: Szymon Janc <szymon.janc@tieto.com>
Cc: linux-bluetooth@vger.kernel.org,
Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Subject: Re: [RFC v2] DBus OutOfBand API update
Date: Mon, 30 Jul 2012 15:52:30 +0300 [thread overview]
Message-ID: <20120730125230.GA16470@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1343391723-32072-1-git-send-email-szymon.janc@tieto.com>
Hi Szymon,
On Fri, Jul 27, 2012, Szymon Janc wrote:
> - short name vs full name distinguish
I don't think we need the distinction. Just support full name.
> - emit DeviceDisappeared when removing oob data?
I suppose we could, not that I feel particularly strongly either way.
> - enable OOB interface only for BLE and/or SSP capable adapters?
I'd just return org.bluez.Error.NotSupported for the methods.
Johan
prev parent reply other threads:[~2012-07-30 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 12:22 [RFC v2] DBus OutOfBand API update Szymon Janc
2012-07-27 12:22 ` [RFC v2] dbusoob: Update API Szymon Janc
2012-07-30 12:52 ` Johan Hedberg [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=20120730125230.GA16470@x220.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon.janc@tieto.com \
--cc=vinicius.gomes@openbossa.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