commit | 70206d660841344dc580a2533678d54a862a7be7 | [log] [tgz] |
---|---|---|
author | Harald Alvestrand <hta@webrtc.org> | Fri Dec 08 07:59:07 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Dec 08 08:47:09 2017 |
tree | 1c3520339c6231f0f4f35d5ef62b015eebff72a8 | |
parent | e08cf3a615cb4f9efeecdba5cea92bc6b7a36e21 [diff] |
Reland "Make RTCP cumulative_lost be a signed value" Instead of modifying the API, we'll add a new function to return the true value, and have a shim that returns what other code expects. > This reverts commit 4c34f435db2b921b82b8be19ee5c1746f46cb188. > > Reason for revert: Broke internal projects. Type mismatch. > > Original change's description: > > Make RTCP cumulative_lost be a signed value > > > > This is formally defined as a signed 24-bit value in RFC 3550 section 6.4.1. > > See RFC 3550 Appendix A.3 for the reason why it may turn negative. > > > > Noticed on discuss-webrtc mailing list. > > > > BUG=webrtc:8626 > > > > Change-Id: I7317f73e9490a876e8445bd3d6b66095ce53ca0a > > Reviewed-on: https://webrtc-review.googlesource.com/30901 > > Reviewed-by: Stefan Holmer <stefan@webrtc.org> > > Commit-Queue: Harald Alvestrand <hta@webrtc.org> > > Cr-Commit-Position: refs/heads/master@{#21142} > > TBR=stefan@webrtc.org,hta@webrtc.org > > Change-Id: I544f7979d584cfb72a2d0d526f4fef84aebeecb3 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: webrtc:8626 > Reviewed-on: https://webrtc-review.googlesource.com/31040 > Reviewed-by: Zhi Huang <zhihuang@webrtc.org> > Commit-Queue: Zhi Huang <zhihuang@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#21144} Change-Id: I95c8c248f4f85c4d1aa2a47424d8c4d954d4ae7a Bug: webrtc:8626 Reviewed-on: https://webrtc-review.googlesource.com/31220 Commit-Queue: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Stefan Holmer <stefan@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21154}
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.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.