commit | 4c85828ab272d9bd58789bad7b135b6287395f97 | [log] [tgz] |
---|---|---|
author | Bjorn A Mellem <mellem@webrtc.org> | Wed Aug 28 22:10:08 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Aug 29 17:30:27 2019 |
tree | dd96b9814b614aa5265e1b016655dbd0539bc8c8 | |
parent | 55dd72c54bee596eb508792e2987f63999b277ba [diff] |
Refactor SCTP data channels to use DataChannelTransportInterface. This change moves SctpTransport to be owned by JsepTransport, which now holds a DataChannelTransport implementation for SCTP when it is used for data channels. This simplifies negotiation and fallback to SCTP. Negotiation can now use a composite DataChannelTransport, just as negotiation for RTP uses a composite RTP transport. PeerConnection also has one fewer way it needs to manage data channels. It now handles SCTP and datagram- or media-transport-based data channels the same way. There are a few leaky abstractions left. For example, PeerConnection calls Start() on the SctpTransport at a particular point in negotiation, but does not need to call this for other transports. Similarly, PC exposes an interface to the SCTP transport directly to the user; there is no equivalent for other transports. Bug: webrtc:9719 Change-Id: I0d3151c48c1a511368277981fc4cf818a9f8ebb4 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/150341 Reviewed-by: Steve Anton <steveanton@webrtc.org> Reviewed-by: Benjamin Wright <benwright@webrtc.org> Commit-Queue: Bjorn Mellem <mellem@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29012}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.