You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2022/09/01 09:50:59 UTC

[GitHub] [mynewt-nimble] ivanholmes commented on issue #1090: GATTS long reads behavior

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

   I ran in to this as well. My callback contained a function that gathered data from an external source which would run multiple times and crash the microcontroller. I must say I found it quite confusing that this was happening, although I have now had a practical education on one of the inner workings of BLE, which is a good thing I suppose!
   
   I think @rojer's idea of buffering the data is a good one. It would also be useful to be able to tell inside the callback function if it is being run for the first time in a long read, the last time, or somewhere in the middle. 
   This would allow the implementation of characteristics that iterate through a data structure, which would be useful in my application.
     


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

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