commit | 6f68254ac3f04d1e9a73beab80c8e80f480b15f8 | [log] [tgz] |
---|---|---|
author | Victor Boivie <boivie@webrtc.org> | Tue Apr 02 08:42:43 2024 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 03 10:13:33 2024 |
tree | 3e05356eb2ed12883bc4bdbd8a3f2fb75ab9d4de | |
parent | d97b6499c3ef7712ccba48cae32192290e622a5a [diff] |
pc: Provide DtlsTransport to SctpTransport constr This code looked a bit weird before this CL - probably because of old refactorings. In JsepTransport constructor, there is a DCHECK assuring that the RTP DTLS transport is always present, so it can be passed directly to the SctpTransport constructor, which avoids having the SetDtlsTransport method in it. Also, in the SctpTransport constructor, there was code that would set the SCTP transport state to `kConnecting` if the DTLS transport was present, but that was dead code, as it was always `nullptr` inside the constructor before this CL. With this CL, it's always present, and the SCTP Transport's state will initially always be `kConnecting` now. Which is a step to deprecating the `kNew` state that doesn't exist in https://w3c.github.io/webrtc-pc/#dom-rtcsctptransportstate. One test case was modified, as it didn't test the reality. The test created a SctpTransport, registered an observer, and added the DTLS transport, and expected to receive a "statechange" from `kNew` (which is not a state that exists in the spec) to `kConnecting`. If the test had tested the opposite ordering - adding the DTLS transport first, and then adding an observer, it wouldn't have experienced this. And since in reality (with the implementation of JsepTransport before and after this CL), it always adds the DTLS transport before any observer is registered. So it wouldn't ever be fired, outside of tests. Bug: webrtc:15897 Change-Id: I6ac24e0a331b686eb400fcf388ece50f2ad46a32 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/345420 Commit-Queue: Victor Boivie <boivie@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#41987}
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.