diff options
authorAnderson Lizardo <>2012-02-27 16:38:11 -0400
committerClaudio Takahasi <>2012-02-28 13:38:19 -0300
commitc0a37bb4c7d0c059c75a1d4045a6f5e18295f12b (patch)
parent64bf4c8937c69098b3f088b3901091d0ae17d1d0 (diff)
bluez: Add brief GAttrib/attio description
1 files changed, 15 insertions, 0 deletions
diff --git a/bluez.tex b/bluez.tex
index ece8ccb..518f70f 100644
--- a/bluez.tex
+++ b/bluez.tex
@@ -88,6 +88,21 @@ The reason behind GATT Profile specific API hide from the user GATT/ATT
internals and move the qualification for the stack instead of the upper
layer GATT applications.
+\subsubsection{GAttrib and ATT connection callbacks}
+Usually, there is only one GAttrib instance for each device connection, which
+is destroyed when the connection is terminated. In order to support a multiple
+profile scenario, GAttrib instances are reference counted. Therefore, profiles
+need to hold at least one reference to a GAttrib for as long as the connection
+is necessary, and drop this reference when the connection is no longer needed.
+It is possible to run custom code when a connection is established or
+terminated by using "ATT connection callbacks" (or attio callbacks, for short).
+These callbacks should be registered whenever the GATT profile has intent to
+communicate with a remote device. When implementing attio callbacks, it is
+important to make sure there is a valid reference to the current GAttrib as
+long as there is a need to use the active connection.
\subsubsection{Generic Attribute API}
Generic Attribute is a GATT client API based on concept of characteristics.