macksal commented on issue #1090: URL: https://github.com/apache/mynewt-nimble/issues/1090#issuecomment-1911801237
Running into this sporadically. It is a confusing behaviour that the offset reads are handled, but the developer still needs to consider this case. Buffering internally in Nimble would be good, but I suppose that could be an equally nasty surprise in a low resource environment. @ivanholmes @rojer did you end up with any workarounds? I'm thinking of caching the value when it's first read, and returning the cached value if it's read again within some time period (e.g. 5 seconds). -- 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]
