From: Claudio Takahasi <claudio.takahasi@openbossa.org>
To: "Ganir, Chen" <chen.ganir@ti.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: GATT Dbus API on BlueZ
Date: Tue, 25 Oct 2011 09:52:48 -0300 [thread overview]
Message-ID: <CAKT1EBeJB2FDrv6Xp_bGV3eFDEe5ecvnBN0rKniYxw5++Q9NfA@mail.gmail.com> (raw)
In-Reply-To: <7769C83744F2C34A841232EF77AEA20C01DCAA8D28@dnce01.ent.ti.com>
Hi Chen Ganir,
On Tue, Oct 25, 2011 at 4:38 AM, Ganir, Chen <chen.ganir@ti.com> wrote:
> Hi.
>
> Currently, the DBUS API for GATT Client will allow discovering characteristics and services, connecting to the peer device if required. However, when the operation is done, the link is dropped (no more attio registered). The only way to register a global gatt_service->attio and keep the connection alive all the time is to register a characteristic watcher. Is there another way to do it ? I'd like to keep the link a live (for example, implementing a proximity link loss profile on top of the DBUS GATT Client) without the need for a watcher.
>
> Thanks,
> Chen Ganir
>
>
At the moment there isn't another way to keep the link up. GATT
Profiles have different connection requirements, you will need a
dynamic mechanism anyway. The callback registration is the mechanism
to inform the core that connection is required. If you keep the
connection always up it will be necessary a function to get access to
the GAttrib instance and a way to notify that the connection has been
established.
I tried to remove the association between GAttrib and GIOChannel. The
idea was to create GAttrib even if the link is disconnected, but the
effort doesn't worth. We will have problems with MTU and GATT
abstractions for read long.
Do have another suggestion to control connections and control the ATT
request/response queue?
BR,
Claudio
next prev parent reply other threads:[~2011-10-25 12:52 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 23:06 [PATCH bluez 0/2] Add BT 3.0+HS signalling definitions Peter Krystad
2011-10-24 23:06 ` [PATCH bluez 1/2] Add L2CAP Create/Move Channel definitions Peter Krystad
2011-10-24 23:06 ` [PATCH bluez 2/2] Add A2MP definitions Peter Krystad
2011-10-25 1:43 ` Add BT 3.0+HS signalling definitions Timur Mehrvarz
2011-10-25 7:38 ` GATT Dbus API on BlueZ Ganir, Chen
2011-10-25 12:52 ` Claudio Takahasi [this message]
2011-10-25 13:19 ` Ganir, Chen
2011-10-26 0:06 ` Claudio Takahasi
2011-10-26 7:20 ` GATT Dbus API on BlueZ - attirbute-api.txt modifications Ganir, Chen
2011-10-27 7:16 ` Mat Martineau
2011-10-27 8:22 ` Ganir, Chen
2011-10-27 11:30 ` Mat Martineau
2011-10-27 13:31 ` Luiz Augusto von Dentz
2011-10-27 13:57 ` Anderson Lizardo
2011-10-27 14:02 ` Anderson Lizardo
2011-10-27 14:58 ` Ganir, Chen
2011-10-27 15:13 ` Anderson Lizardo
2011-10-27 15:18 ` Ganir, Chen
2011-10-27 15:35 ` Anderson Lizardo
2011-10-27 15:06 ` Ganir, Chen
2011-10-27 15:29 ` Anderson Lizardo
2011-10-27 15:48 ` Ganir, Chen
2011-10-27 16:29 ` Anderson Lizardo
2011-10-27 16:47 ` Ganir, Chen
2011-10-27 17:32 ` Anderson Lizardo
2011-10-30 6:56 ` Ganir, Chen
2011-10-30 14:23 ` Anderson Lizardo
2011-10-30 15:48 ` Ganir, Chen
2011-10-30 18:02 ` Anderson Lizardo
2011-10-31 6:38 ` Ajay Pillai
2011-10-31 6:57 ` Ganir, Chen
2011-10-31 8:04 ` Ajay Pillai
2011-10-31 10:47 ` Anderson Lizardo
2011-10-31 7:19 ` Ganir, Chen
2011-10-31 11:07 ` Anderson Lizardo
2011-10-31 13:35 ` Ajay Pillai
2011-10-31 14:53 ` Luiz Augusto von Dentz
2011-10-28 16:19 ` Brian Gix
2011-10-28 20:09 ` Anderson Lizardo
2011-10-27 13:32 ` Anderson Lizardo
2011-10-31 17:41 ` Tsai, Mike
2012-01-11 14:25 ` GATT Dbus API on BlueZ Vijaykumar Dadmode
2012-01-11 14:57 ` Claudio Takahasi
2011-10-25 14:41 ` Add BT 3.0+HS signalling definitions Peter Krystad
2011-10-26 0:15 ` Timur Mehrvarz
2011-10-26 7:54 ` Andrei Emeltchenko
2011-10-27 13:39 ` BT 3.0+HS Timur Mehrvarz
2011-10-27 16:46 ` tim.howes
2011-11-03 16:38 ` Timur Mehrvarz
2011-10-26 7:36 ` [PATCH bluez 0/2] Add BT 3.0+HS signalling definitions Andrei Emeltchenko
2011-10-26 17:44 ` Peter Krystad
2011-10-27 8:00 ` 'Andrei Emeltchenko'
2011-10-28 0:23 ` Peter Krystad
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=CAKT1EBeJB2FDrv6Xp_bGV3eFDEe5ecvnBN0rKniYxw5++Q9NfA@mail.gmail.com \
--to=claudio.takahasi@openbossa.org \
--cc=chen.ganir@ti.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 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).