From: Andrejs Hanins <andrejs.hanins@ubnt.com>
To: dogan yazar <doganyazar@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Detect client connection using dbus api
Date: Thu, 18 Jun 2015 12:19:41 +0300 [thread overview]
Message-ID: <55828D2D.8040208@ubnt.com> (raw)
In-Reply-To: <CANzaTi6FBqUARP7iqSMfYMJmE6L-6cp2DKAzrMBzn948+dSs4w@mail.gmail.com>
On 06/18/2015 12:02 PM, dogan yazar wrote:
> Thanks for the answer. How does it differentiate if it is a client or
> a server? If bluez work as a client and connect to a device, same
> property will be set anyway.
Just an idea: If BlueZ is a client, then someone does initiate the connect
explicitly by calling Connect() D-Bus method on a given device path, so we
know whom we are connecting to. But there may be a better way...
>
> On Thu, Jun 18, 2015 at 10:31 AM, Andrejs Hanins
> <andrejs.hanins@ubnt.com> wrote:
>> Hi,
>>
>> On 06/18/2015 11:24 AM, dogan yazar wrote:
>>> I use gatt-api to register my services but then could not find a way
>>> to detect that a client is connected and discovering my services.
>>> Any ideas?
>> In case of connected client, there will be a org.bluez.Device1 object created
>> with Connected propery set to "true". So if you would like to track connect/disconnect
>> events, you should listed for this property changes. At least, this is how I do it.
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
next prev parent reply other threads:[~2015-06-18 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 8:24 Detect client connection using dbus api dogan yazar
2015-06-18 8:31 ` Andrejs Hanins
2015-06-18 9:02 ` dogan yazar
2015-06-18 9:19 ` Andrejs Hanins [this message]
2015-06-22 9:28 ` dogan yazar
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=55828D2D.8040208@ubnt.com \
--to=andrejs.hanins@ubnt.com \
--cc=doganyazar@gmail.com \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.