From: Marcel Holtmann <marcel@holtmann.org>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC BlueZ 0/6] LE Connection Establishment fixes
Date: Fri, 25 Jan 2013 12:30:10 +0100 [thread overview]
Message-ID: <1359113410.8989.3.camel@aeonflux> (raw)
In-Reply-To: <1359083227-13122-1-git-send-email-vinicius.gomes@openbossa.org>
Hi Vinicius,
> Sending this as a RFC because I don't know if this is what you guys
> had in mind.
>
> Patches 1/6/ and 2/6 are simple enough fixes and should be considered
> for inclusion, perhaps 6/6 as well, but the improvement is
> non-functional.
>
> The only problem with this aproach that I found while testing is the
> problem exposed on the message of commit 5/6: If the remote device is
> out of range during pairing any connection attempt will fail until the
> Connection Complete event comes (with an error). This is the reason
> that we put the devices in the connect list before pairing.
>
> Is this reason enough to have the device put in the connect list
> during pairing?
such a reasoning is pretty much wrong on all levels. An out of range
device might never come back in range and you end up with a device on
the connect list forever. And if it ever comes back, we end up with some
unexpected connection attempt to that device.
The only sane approach would have been to add a timeout and just abort
the pairing attempt after it. Everything else is just trying to fix a
symptom and making it actually worse while doing so.
Regards
Marcel
prev parent reply other threads:[~2013-01-25 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 3:07 [RFC BlueZ 0/6] LE Connection Establishment fixes Vinicius Costa Gomes
2013-01-25 3:07 ` [RFC BlueZ 1/6] device: Fix invalid memory access during Find Included Vinicius Costa Gomes
2013-01-25 7:07 ` Johan Hedberg
2013-01-25 3:07 ` [RFC BlueZ 2/6] device: Fix memory leak while storing GATT capable devices Vinicius Costa Gomes
2013-01-25 7:08 ` Johan Hedberg
2013-01-25 3:07 ` [RFC BlueZ 3/6] device: Clean up device_att_connect() Vinicius Costa Gomes
2013-01-25 3:07 ` [RFC BlueZ 4/6] device: Rename device_att_connect to device_connect_le Vinicius Costa Gomes
2013-01-25 7:32 ` Johan Hedberg
2013-01-25 3:07 ` [RFC BlueZ 5/6] core: Add a way to connect to LE devices Vinicius Costa Gomes
2013-01-25 3:07 ` [RFC BlueZ 6/6] gas: Move all the code to only one file Vinicius Costa Gomes
2013-01-25 7:36 ` Johan Hedberg
2013-01-25 10:55 ` Anderson Lizardo
2013-01-25 7:12 ` [RFC BlueZ 0/6] LE Connection Establishment fixes Johan Hedberg
2013-01-25 9:55 ` Johan Hedberg
2013-01-25 11:30 ` Marcel Holtmann [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=1359113410.8989.3.camel@aeonflux \
--to=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).