You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@mynewt.apache.org by "vandy (via GitHub)" <gi...@apache.org> on 2024/08/10 08:17:13 UTC

Re: [I] GATTS long reads behavior [mynewt-nimble]

vandy commented on issue #1090:
URL: https://github.com/apache/mynewt-nimble/issues/1090#issuecomment-2280244408

   @ivanholmes, @macksal, @rojer, I believe buffering the data inside the nimble stack is not an option here. Because it's up to the client to decide whether it wants to and will read the whole attribute or not, so there is no guarantee that after the first read request there would be other.
   
   As provided in the comments `offset` field in `ble_gatt_access_ctxt` struct could indicate the long attribute read procedure. I've made a pull request on this #1846.


-- 
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: notifications-unsubscribe@mynewt.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org