| commit | 407367d053dffe4653732e3f6b5acac28caa1382 | [log] [tgz] |
|---|---|---|
| author | Mirko Bonadei <mbonadei@webrtc.org> | Mon Feb 12 08:52:04 2024 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Feb 12 10:07:04 2024 |
| tree | 5f6267b22171a7fc412620027c6edf91258ff118 | |
| parent | 52fec7d3e9c8503d5c7455398784a874a1fed90f [diff] |
Revert "Let port allocator create ice tie breaker" This reverts commit 3f3f991c03bb4073a06da37c822daaa9deed9307. Reason for revert: API breaking change on PortAllocatorSession. Is it possible to duplicate the ctor of PortAllocatorSession and remove the deprecated one (the one without ice_tiebreaker) in another CL? 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: I342c9a96ac1909244aedea6a7779f5682088a5fc Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/339280 Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Björn Terelius <terelius@webrtc.org> Owners-Override: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/main@{#41715}
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.