commit | 1c7ecefbe7ed08c583d3c403a6881d18a0d0f1ca | [log] [tgz] |
---|---|---|
author | Taylor Brandstetter <deadbeef@webrtc.org> | Wed Aug 11 19:38:35 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 11 21:50:08 2021 |
tree | e60e2a3797491b4a9e76173e879426fb18af2c01 | |
parent | b7eb18da6e16ce2015b029f45408e5171d18c977 [diff] |
Reland "Modify Bundle logic to not add & destroy extra transport at add-track" This relands commit I41cae74605fecf454900a958776b95607ccf3745, after reverting it in order to merge the revert to M93 (the deadline for which is now exceeded). 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} Bug: webrtc:12837 Change-Id: I30a8f03165ab797ed766b51c4eb15c2a9cecb5ed Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/228500 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34727}
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.