Vincent Coubard
Vincent Coubard
This PR fix reporting of notification and indication.
The timeout in the scan parameters is not handled at all, the scan operation timeout doesn't timeout at the expected time, in fact it doesn't timeout at all.
With the current API their is no way to know if an error occur during the following GattClient procedures: - `read`: If a read procedure fail, it should be possible...
It would be nice if the "ScanResponse" API mirrored the "AdvertisingPayload" API. In this regard, functions: `setScanResponse`, `getScanResponse` and `updateScanResponse` are missing from the current GAP API
The UART service can only be used with one connection at the moment, as soon as a second connection happen on the device, the write operation stop working (see https://developer.mbed.org/forum/team-63-Bluetooth-Low-Energy-community/post/40093/...
Each `GattCharacteristic` store two FunctionPointersWithContext, one for the readAuthorization callback and one for the writeAuthorization callback. This waste some space given that: - In practice these authorizations are not always...
The current GattClient API does not provide any way to catch a failure during a GattClient procedure. The following procedure miss this feature: - Primary service discovery - Characteristic discovery...
Some write operations are missing from the current implementation: - signed write command - write blob operations: - prepare write request - execute (commit) write request
Deprecation of features of BLE API can be more visible to end user. There is two ways to improve this: - Documentation: doxygen support a directive for deprecated elements: `\deprecated`....