You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the gatt-api side, the MTU is part of the ReadValue method as an option. I did not find the error behavior documented, but my observation is that responding with more bytes than the MTU indicates just leads to transmission of a truncated response, whereas I think good practice in Rust would be to indicate this through an error.
The text was updated successfully, but these errors were encountered:
chrysn
added a commit
to chrysn-pull-requests/bluster
that referenced
this issue
Aug 3, 2022
When handling a ReadRequest, neither can the user see the the MTU, nor is it checked whether the value passed in is short enough:
On the gatt-api side, the MTU is part of the ReadValue method as an option. I did not find the error behavior documented, but my observation is that responding with more bytes than the MTU indicates just leads to transmission of a truncated response, whereas I think good practice in Rust would be to indicate this through an error.
The text was updated successfully, but these errors were encountered: