commit | 49c0869825c4c6165d64afc1002d40ecb68240e5 | [log] [tgz] |
---|---|---|
author | philipel <philipel@webrtc.org> | Tue May 24 08:49:43 2016 |
committer | Commit bot <commit-bot@chromium.org> | Tue May 24 08:49:46 2016 |
tree | c7b655d77c69139e4aa25c5b1569c5904dab4d6d | |
parent | 5ceaaae3689cac9ae10dc7caf5802e8d6e0c7a99 [diff] |
Revert of Change initial DTLS retransmission timer from 1 second to 50ms. (patchset #2 id:20001 of https://codereview.webrtc.org/1981463002/ ) Reason for revert: Seems like this CL cause DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable to consistently fail on Win DrMemory Full and for DtlsTransportChannelTest.TestReceiveClientHelloBeforeRemoteFingerprint DtlsTransportChannelTest.TestReceiveClientHelloBeforeWritable to consistently fail on Linux Memcheck Original issue's description: > Change initial DTLS retransmission timer from 1 second to 50ms. > > This will help ensure a timely DTLS handshake when there's packet > loss. It will likely result in spurious retransmissions (since the > RTT is usually > 50ms), but since exponential backoff is still used, > there will at most be ~4 extra retransmissions. For a time-sensitive > application like WebRTC this seems like a reasonable tradeoff. > > R=juberti@chromium.org, juberti@webrtc.org, pthatcher@webrtc.org > > Committed: https://crrev.com/1e435628366fb9fed71632369f05928ed857d8ef > Cr-Commit-Position: refs/heads/master@{#12853} TBR=pthatcher@webrtc.org,juberti@webrtc.org,juberti@chromium.org,deadbeef@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review-Url: https://codereview.webrtc.org/2002403002 Cr-Commit-Position: refs/heads/master@{#12864}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.