| commit | 6e9dccadeea4517e0f85b62be35fcda5affcfaad | [log] [tgz] |
|---|---|---|
| author | Philipp Hancke <philipp.hancke@googlemail.com> | Thu Oct 23 17:01:56 2025 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 24 08:21:21 2025 |
| tree | c157e90b3eac210b1e41b35c7d27e7faf9263a4d | |
| parent | 512a5cf31f8caec7bca6b45c569ba60ae232d9f2 [diff] |
pc: add "always negotiate datachannels" options to RTCConfiguration Add a boolean option to always negotiate SCTP m-line even when no datachannel have been added to the peerconnection. This avoids creating a throwaway datachannel and also allows avoiding the backward compat "put datachannel last" provision described in https://datatracker.ietf.org/doc/html/rfc8829#name-initial-offers "Lastly, if any datachannel has been created..." and putting that m-line before any RTP m-lines. Unlike RTP contents, data channels are rarely rejected which avoids issues with rejecting the first media section which is better for the behavior described in https://datatracker.ietf.org/doc/html/rfc8843#name-rejecting-a-media-descripti It is RECOMMENDED that the suggested offerer-tagged "m=" section be a bundled "m=" section that the offerer believes is unlikely that the answerer will reject or move out of the BUNDLE group W3C spec link: https://w3c.github.io/webrtc-extensions/#always-negotiating-datachannels Reupload of https://webrtc-review.googlesource.com/c/src/+/405044 Co-authored-by: phancke@meta.com Bug: chromium:433898678 Change-Id: I6862b952c305ba11346475227f342b3cebf9031b Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/417783 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com> Reviewed-by: Guido Urdaneta <guidou@webrtc.org> Cr-Commit-Position: refs/heads/main@{#46025}
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.