From: Johan Hedberg <johan.hedberg@gmail.com>
To: Mark Spruiell <mes@zeroc.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: SDP query via D-Bus?
Date: Tue, 29 Sep 2015 09:49:37 +0300 [thread overview]
Message-ID: <20150929064937.GA26120@t440s.lan> (raw)
In-Reply-To: <CABOZqnjSPbO-cNkSryq5GXBKTqtE-1TPMKMgTAwtd9YoO4i-4A@mail.gmail.com>
Hi Mark,
On Mon, Sep 28, 2015, Mark Spruiell wrote:
> We currently use sdp_connect and sdp_service_search_attr_req to
> determine the RFCOMM channel associated with a service on a remote
> device.
>
> Does the D-Bus API provide an equivalent way to discover this information?
Not directly, but there's a more convenient & higher level API available
if you look at doc/profile-api.txt and test/test-profile. This will not
only look up the RFCOMM channel for you, but also go ahead and connect
to the service and then give you back the connected RFCOMM socket over
D-Bus.
Johan
next prev parent reply other threads:[~2015-09-29 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 21:14 SDP query via D-Bus? Mark Spruiell
2015-09-29 6:49 ` Johan Hedberg [this message]
2015-09-29 21:01 ` Mark Spruiell
2015-09-30 4:34 ` Johan Hedberg
2015-10-07 17:16 ` Mark Spruiell
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=20150929064937.GA26120@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mes@zeroc.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;
as well as URLs for NNTP newsgroup(s).