dcsctp: Correct safety tag for MaxRetransmits
By a copy-paste accident, it used the same as TimeMs. Bug: None Change-Id: Ic290cd256b1b89f0dc0893582252c3248a1ee28a Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/259861 Commit-Queue: Victor Boivie <boivie@webrtc.org> Auto-Submit: Victor Boivie <boivie@webrtc.org> Reviewed-by: Florent Castelli <orphis@webrtc.org> Commit-Queue: Florent Castelli <orphis@webrtc.org> Cr-Commit-Position: refs/heads/main@{#36617}
This commit is contained in:
parent
b844dd8465
commit
7e11ea2d30
@ -107,10 +107,11 @@ constexpr inline DurationMs operator-(TimeMs lhs, TimeMs rhs) {
|
||||
|
||||
// The maximum number of times the socket should attempt to retransmit a
|
||||
// message which fails the first time in unreliable mode.
|
||||
class MaxRetransmits : public webrtc::StrongAlias<class TimeMsTag, uint16_t> {
|
||||
class MaxRetransmits
|
||||
: public webrtc::StrongAlias<class MaxRetransmitsTag, uint16_t> {
|
||||
public:
|
||||
constexpr explicit MaxRetransmits(const UnderlyingType& v)
|
||||
: webrtc::StrongAlias<class TimeMsTag, uint16_t>(v) {}
|
||||
: webrtc::StrongAlias<class MaxRetransmitsTag, uint16_t>(v) {}
|
||||
|
||||
// There should be no limit - the message should be sent reliably.
|
||||
static constexpr MaxRetransmits NoLimit() {
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user