summaryrefslogtreecommitdiff
path: root/doc/gatt-api.txt
diff options
context:
space:
mode:
authorGrzegorz Kolodziejczyk <grzegorz.kolodziejczyk@codecoup.pl>2018-03-20 15:05:17 +0100
committerSzymon Janc <szymon.janc@codecoup.pl>2018-03-21 10:47:07 +0100
commit4c22678e960a5bd89aed0717cc6ef863467b9014 (patch)
treeb16e9873f6ecb203e1532174318e4bb1cbd34651 /doc/gatt-api.txt
parent1abee58711bd10534d958e0fefe551b1d70dde2b (diff)
downloadbluez-4c22678e960a5bd89aed0717cc6ef863467b9014.tar.gz
gatt: Add org.bluez.Error.InvalidOffset for long read procedure
This patch adds handling of invalid offset error for gatt database in case if offset in read blob would be invalid. "The Read Blob Request is repeated until the Read Blob Response’s Part Attribute Value parameter is zero or an Error Response is sent by the server with the Error Code set to Invalid Offset." Bluetooth Core 5.0, 4.12.2 "If the prepare Value Offset is greater than the current length of the attribute value then all pending prepare write values shall be discarded for this client, the queue shall be cleared and then an Error Response shall be sent with the «Invalid Offset»." Bluetooth Core 5.0, 3.4.6.3
Diffstat (limited to 'doc/gatt-api.txt')
-rw-r--r--doc/gatt-api.txt1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/gatt-api.txt b/doc/gatt-api.txt
index 9579381a5..f58de23c3 100644
--- a/doc/gatt-api.txt
+++ b/doc/gatt-api.txt
@@ -74,6 +74,7 @@ Methods array{byte} ReadValue(dict options)
org.bluez.Error.InProgress
org.bluez.Error.NotPermitted
org.bluez.Error.NotAuthorized
+ org.bluez.Error.InvalidOffset
org.bluez.Error.NotSupported
void WriteValue(array{byte} value, dict options)