vandy opened a new pull request, #1846: URL: https://github.com/apache/mynewt-nimble/pull/1846
To obtain an attribute value when the attribute size is greater than configured MTU long attribute read procedure could be used. A client sends consecutive `ATT_READ_BLOB_REQ` requests (passing along an offset) to consume the attribute value. The offset is used internally in the nimble stack but is not passed to a user provided access callback in a GATT characteristic description. This callback is called the same number of times as the number of blob requests, but it's not possible to say whether it's a first request (or maybe just `ATT_READ_REQ`) or consecutive request. The provided offset could indicate this situation to the app developer. However, Core Spec 5.4 Vol 3 Part F 3.4.4.5 notes: > Note: The value of a Long Attribute may change between the server receiving one ATT_READ_BLOB_REQ PDU and the next ATT_READ_BLOB_REQ PDU. A higher layer specification should be aware of this and define appropriate behavior. It's up to a developer to decide what to do, when consecutive (long attribute) reading takes place. This was discussed in #1090. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
