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 2019/08/13 20:33:31 UTC

[GitHub] [mynewt-nimble] hardik-proxy opened a new pull request #555: nimble/mesh: configurable segment retransmist attempts

hardik-proxy opened a new pull request #555: nimble/mesh: configurable segment retransmist attempts
URL: https://github.com/apache/mynewt-nimble/pull/555
 
 
   Current SEG_RETRANSMIT_ATTEMPTS value is defined as 4. And hence, while sending non-ack segmented messages, each segment is being re-transmitted 4 times. When it comes, to the timing I observed that a message with three segments takes at least 8-15 seconds between successive re-transmissions. For reliability, if the whole message is being transmitted multiple times, I believe segment re-transmissions becomes redundant (please correct me if I am wrong) and thus SEG_RETRANSMIT_ATTEMPTS can be set to lower value to reduce the time between successive re-transmissions.
   
   As corrected by @rymanluk minimum suggested by the spec is 2.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services