Lancaster University / BLE_API

Lancaster University's fork of the mbed BLE API. Lives on github, https://github.com/lancaster-university/BLE_API

Dependents:   microbit-dal microbit-dal microbit-ble-open microbit-dal ... more

Fork of BLE_API by Bluetooth Low Energy

Diff: public/DiscoveredCharacteristic.h

Revision:
499:db9bc083f91e
Parent:
497:926d444599e8
Child:
501:ff6801633d2c
--- a/public/DiscoveredCharacteristic.h	Fri Jun 19 15:52:03 2015 +0100
+++ b/public/DiscoveredCharacteristic.h	Fri Jun 19 15:52:03 2015 +0100
@@ -81,11 +81,11 @@
      * @param  value
      *           The bytes being written.
      *
-     * @note   It is important to note that a write without response will
-     *         <b>consume an application buffer</b>, and will therefore
-     *         generate a onDataSent() callback when the packet has been
-     *         transmitted. The application should ensure that the buffer is
-     *         valid until the callback.
+     * @note   It is important to note that a write without response will generate
+     *         an onDataSent() callback when the packet has been transmitted. There
+     *         will be a BLE-stack specific limit to the number of pending
+     *         writeWoResponse operations; the user may want to use the onDataSent()
+     *         callback for flow-control.
      *
      * @retval BLE_ERROR_NONE Successfully started the Write procedure, else
      *         BLE_ERROR_INVALID_STATE if some internal state about the connection is invalid, or
@@ -95,6 +95,7 @@
      */
     ble_error_t writeWoResponse(uint16_t length, const uint8_t *value) const;
 
+
     static void setupOnDataRead(ReadCallback_t callback) {
         onDataReadCallback = callback;
     }