2/MVDS: MVDS max retries

[decanus]

trafficstars

Problem

Certain applications like ultralight beam may see peers changing the method of which they are accessible frequently without notifying peers.

Solution

A max retries option is added which informs the MVDS node how many times a message should be retransmissioned, if it can not be sent to the peer in those retries the application is notified and can then handle this gracefully by for example trying to reach the peer through some other means or delaying until it knows that a peer is online again.

Notes

Due to how ultralight beam handles peers, this may not be that relevant assuming we send to a public key.

[oskarth]

Is this definitely not solved with exponential delay? How is this dealt with in e.g. TCP?

[jimstir]

Closing, 2/MVDS is in stable status.