commit | da4f09315f6daa2bc9f66150e4a508bac53cd19d | [log] [tgz] |
---|---|---|
author | Bjorn A Mellem <mellem@webrtc.org> | Tue Jul 30 15:34:03 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Aug 01 01:08:24 2019 |
tree | 9af57b1a0db525f926059f2e1d9096059f26e754 | |
parent | fd643a4782c9d70b683b8638e4f71e06e3650680 [diff] |
Reland "Only include payload in bytes sent/received." This is a reland of 74a1b4b1321b426392d4c32e4a02361226ad5358 Original change's description: > Only include payload in bytes sent/received. > > According to https://www.w3.org/TR/webrtc-stats/#sentrtpstats-dict* and > https://tools.ietf.org/html/rfc3550#section-6.4.1, the bytes sent > statistic should not include headers or padding. > > Similarly, according to > https://www.w3.org/TR/webrtc-stats/#inboundrtpstats-dict*, bytes > received are calculated the same way as bytes sent (eg. not including > padding or headers). > > This change stops adding padding and headers to these statistics. > > Bug: webrtc:8516,webrtc:10525 > Change-Id: I891ad5a11a493cc3212afe93e13f62795bf4031f > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/146180 > Reviewed-by: Stefan Holmer <stefan@webrtc.org> > Reviewed-by: Erik Språng <sprang@webrtc.org> > Reviewed-by: Steve Anton <steveanton@webrtc.org> > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> > Reviewed-by: Oskar Sundbom <ossu@webrtc.org> > Commit-Queue: Bjorn Mellem <mellem@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#28647} Bug: webrtc:8516, webrtc:10525 Change-Id: Iaa1613e5becdfaa0af0f6b9f00e5b871937a719c Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/147520 Reviewed-by: Steve Anton <steveanton@webrtc.org> Reviewed-by: Fredrik Solenberg <solenberg@webrtc.org> Commit-Queue: Bjorn Mellem <mellem@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28731}
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.