From: Johan Hedberg <johan.hedberg@gmail.com>
To: Claudio Takahasi <claudio.takahasi@openbossa.org>
Cc: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 0/6] Move Attrib client (including: should we disconnect or not?)
Date: Mon, 28 Mar 2011 23:48:06 +0300 [thread overview]
Message-ID: <20110328204806.GA29708@jh-x301> (raw)
In-Reply-To: <AANLkTin8et-m0pczJKm9y3z-EHqQdN-49KkAXGGm8jqO@mail.gmail.com>
Hi Claudio & Vinicius,
> >> The move itself is pretty simple, but when implementing it, I took a decision
> >> and I would like to hear your opinion about it.
> >
> > There were problems with some useless includes. I will send another version
> > soon. But the question below remains.
> >
> >>
> >> With this patch series, the behaviour is that we never disconnect from
> >> a LE device unless we are told so, i.e. org.bluez.Device.Disconnect(),
> >> is that what is expected from us?
>
> In my opinion, the profiles should define how to manage connections.
> For LE re-connections should be avoided since the remote disables the
> advertising when the connection is established.
> Keep the link up seems to be acceptable for now, but for the final
> solution we need to disconnect based on the registered "watchers" and
> profile inputs. Some profiles such as proximity keeps the devices
> always connected and auto-reconnect, others require user interaction.
Sounds good enough to me, i.e. let's keep "connected until an explicit
disconnect request from the user" the default for now.
Johan
prev parent reply other threads:[~2011-03-28 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 0:01 [PATCH 0/6] Move Attrib client (including: should we disconnect or not?) Vinicius Costa Gomes
2011-03-26 0:01 ` [PATCH 1/6] Move Attrib client to the core Vinicius Costa Gomes
2011-03-26 0:01 ` [PATCH 2/6] Register Attrib interface when loading device from storage Vinicius Costa Gomes
2011-03-26 0:01 ` [PATCH 3/6] Register Attrib interface after Primary Service discovery Vinicius Costa Gomes
2011-03-26 0:01 ` [PATCH 4/6] Remove _init and _exit methods from Attrib client Vinicius Costa Gomes
2011-03-26 0:01 ` [PATCH 5/6] Add support for re-using the attrib channel Vinicius Costa Gomes
2011-03-26 0:01 ` [PATCH 6/6] Fix disconnecting when primary service discovery is done Vinicius Costa Gomes
2011-03-28 20:33 ` [PATCH 0/6] Move Attrib client (including: should we disconnect or not?) Vinicius Costa Gomes
2011-03-28 20:40 ` Claudio Takahasi
2011-03-28 20:48 ` 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=20110328204806.GA29708@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=claudio.takahasi@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
--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