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/03/14 13:15:25 UTC

[GitHub] [mynewt-nimble] sjanc commented on issue #1206: BLE Nimble SPP packet fragmentation (packet > MTU)

sjanc commented on issue #1206:
URL: https://github.com/apache/mynewt-nimble/issues/1206#issuecomment-1066771683


   this is expected, ATT MTU includes ATT header (opcode [1byte]+ handle [2 bytes])
   
   regarding fragmentation,   when writing >MTU bytes of data to serwer client is doing long write operation, which consists on multiple att prepare writes.  On notification this is not automated,  ie server sends notification up to MTU bytes, and then it is client responsibility to do read blob with proper offset to read remaining data (and I think that in NimBLE it is up to application to decide if it wants to read the rest or not)


-- 
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