commit | e3fb8122aa218bfc90b57515c6fb118679e6f297 | [log] [tgz] |
---|---|---|
author | Philipp Hancke <phancke@microsoft.com> | Mon Feb 12 11:21:16 2024 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 12 14:47:12 2024 |
tree | 986186013c65c4d5aa07a8fbd668539f584f9094 | |
parent | 1cce1d7ddcbde3a3648007b5a131bd0c2638724b [diff] |
Reland "Let port allocator create ice tie breaker" This is a reland of commit 3f3f991c03bb4073a06da37c822daaa9deed9307 Original change's description: > Let port allocator create ice tie breaker > > Moves the responsibility for creating the ICE tie breaker from the JSEP transport controller to the port allocator. This will allow a future change to separate the ICE tie breaker (which is sent over the network and hence known to the peer) from the "port allocator random" (that is used to seed the ICE candidate foundation crc32 checksum) as an implementation detail. > > BUG=webrtc:14626 > > Change-Id: I3a9a0980238d6108b1b154f45de2975b08793b1c > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/281660 > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Commit-Queue: Philipp Hancke <phancke@microsoft.com> > Cr-Commit-Position: refs/heads/main@{#41707} Bug: webrtc:14626 Change-Id: Id3c8f257c5611958551bd66d7ce7a885bf8ba2f9 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/339320 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Philipp Hancke <phancke@microsoft.com> Cr-Commit-Position: refs/heads/main@{#41720}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.