in the past this was interpreted as "after encryption and in the network process" but that did not make much difference. Doing this after pacing is still a good idea Bug: webrtc:487743907 Change-Id: I3b14225c29c210db0b12b54ca51814fe2836e1e8 No-Try: true Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/452960 Reviewed-by: Fredrik Solenberg <solenberg@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com> Cr-Commit-Position: refs/heads/main@{#47081} |
||
|---|---|---|
| .. | ||
| android | ||
| development | ||
| ios | ||
| rtp-hdrext | ||
| sdp-ext | ||
| logging.md | ||
| README.md | ||
WebRTC native code
The WebRTC Native Code package is meant for browser developers who want to integrate WebRTC. Application developers are encouraged to use the WebRTC API instead.
The WebRTC native code can be found at https://webrtc.googlesource.com/src.
The change log is available at https://webrtc.googlesource.com/src/+log
Please read the License & Rights and FAQ before downloading the source code.
The WebRTC issue tracker can be used for submitting bugs found in native code.