From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jakub Pawlowski <jpawlowski@google.com>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC] Add new method to DBus API: DiscoverServiceByUUID
Date: Sun, 31 May 2015 09:55:05 +0700 [thread overview]
Message-ID: <20150531025505.GA23991@t440s> (raw)
In-Reply-To: <CAD0=r8wDGKw4DRnEAsZqNvMc05CGnjz7HVFc6MTQZi74L9xC1Q@mail.gmail.com>
Hi Jakub,
On Thu, May 28, 2015, Jakub Pawlowski wrote:
> > 1. Instead of just 1 method there is at least 2, but Connect depends
> > on what has been discovered first so you are adding a D-Bus round
> > trips.
>
> Yes, I'm probably adding one round trip. It might hovewer be avoided.
> To avoid additional roundtrip there should be two methods:
> Connect() that just works right now, and ConnectToUUID(uuid) that
> would connect, and then do "Find By Type Value Request". I think that
> this solution wouldn't be that clean, and would be problematic to
> discover rest of services.
We already have this "ConnectToUUID" method in the form of
Device1.ConnectProfile, don't we? It was originally designed for BR/EDR,
but seems to have at least some code for LE as well. If it's not working
as desired for LE it's probably something worth fixing.
Johan
next prev parent reply other threads:[~2015-05-31 2:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 20:44 [RFC] Add new method to DBus API: DiscoverServiceByUUID Jakub Pawlowski
2015-05-28 21:32 ` Luiz Augusto von Dentz
2015-05-28 22:25 ` Jakub Pawlowski
2015-05-29 8:35 ` Luiz Augusto von Dentz
2015-05-31 2:55 ` Johan Hedberg [this message]
2015-06-01 17:25 ` Jakub Pawlowski
2015-06-01 18:22 ` Luiz Augusto von Dentz
2015-06-01 21:42 ` Arman Uguray
2015-06-02 14:51 ` Luiz Augusto von Dentz
2015-06-09 10:48 ` Luiz Augusto von Dentz
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=20150531025505.GA23991@t440s \
--to=johan.hedberg@gmail.com \
--cc=jpawlowski@google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox