From 7bc3d0031395dcf700b005c4933102f8897350f6 Mon Sep 17 00:00:00 2001 From: ortuno Date: Thu, 10 Mar 2016 21:37:19 -0800 Subject: bluetooth: Clarify how StartNotifySession function works And what happens when the device doesn't have the expected descriptor. BUG=591864 Review URL: https://codereview.chromium.org/1758293003 Cr-Commit-Position: refs/heads/master@{#380538} --- device/bluetooth/bluetooth_gatt_characteristic.h | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'device') diff --git a/device/bluetooth/bluetooth_gatt_characteristic.h b/device/bluetooth/bluetooth_gatt_characteristic.h index 6dabe87..8cce601 100644 --- a/device/bluetooth/bluetooth_gatt_characteristic.h +++ b/device/bluetooth/bluetooth_gatt_characteristic.h @@ -181,6 +181,12 @@ class DEVICE_BLUETOOTH_EXPORT BluetoothGattCharacteristic { // notifications/indications. On success, the characteristic starts sending // value notifications and |callback| is called with a session object whose // ownership belongs to the caller. |error_callback| is called on errors. + // + // Writes to the Client Characteristic Configuration descriptor to enable + // notifications/indications. Core Bluetooth Specification [V4.2 Vol 3 Part G + // Section 3.3.1.1. Characteristic Properties] requires this descriptor to be + // present when notifications/indications are supported. If the descriptor is + // not present |error_callback| will be run. virtual void StartNotifySession(const NotifySessionCallback& callback, const ErrorCallback& error_callback) = 0; -- cgit v1.1