commit | a03d49422488ba84c14a2378c35e061caa98e938 | [log] [tgz] |
---|---|---|
author | Taylor Brandstetter <deadbeef@webrtc.org> | Fri Aug 06 19:58:10 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 06 21:43:09 2021 |
tree | c85efdbd78183b8de58aa808330cb2677e8249b9 | |
parent | 99fb5945b9c278cf33ef434ebacd5dfb9bde865d [diff] |
Revert "Modify Bundle logic to not add & destroy extra transport at add-track" This reverts commit I41cae74605fecf454900a958776b95607ccf3745 Reason for revert: Needed in order to cherry pick this revert into M93, in order to fix crbug.com/1236202. Original change description: > If a bundle is established, then per JSEP, the offerer is required to > include the new track in the bundle, and per BUNDLE, the answerer has > to either accept the track as part of the bundle or reject the track; > it cannot move it out of the group. So we will never need the transport. > > Bug: webrtc:12837 > Change-Id: I41cae74605fecf454900a958776b95607ccf3745 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/221601 > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Commit-Queue: Harald Alvestrand <hta@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#34290} TBR=hta@webrtc.org Bug: webrtc:12837, chromium:1236202 Change-Id: Ie59e2ad5168e6829eefa67b1031b8f400ed66507 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/227822 Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34669}
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.