| commit | c0dad89bed44c05a8a4c01f6c7a0fd58912479aa | [log] [tgz] |
|---|---|---|
| author | deadbeef <deadbeef@webrtc.org> | Wed Jan 04 20:28:21 2017 -0800 |
| committer | Commit bot <commit-bot@chromium.org> | Thu Jan 05 04:28:21 2017 +0000 |
| tree | 12c3a28a45cc551717440f77f2cbd23019f63165 | |
| parent | e9bbde583043051e9c55f30b938efc29db28b962 [diff] |
Revert of Separating SCTP code from BaseChannel/MediaChannel. (patchset #14 id:240001 of https://codereview.webrtc.org/2564333002/ ) Reason for revert: Hitting DCHECK in chromium's WebrtcTransportTest.TerminateDataChannel and WebrtcTransportTest.DataStreamLate. Will investigate and reland. Original issue's description: > Separating SCTP code from BaseChannel/MediaChannel. > > The BaseChannel code is geared around RTP; the presence of media engines, > send and receive streams, SRTP, SDP directional attribute negotiation, etc. > It doesn't make sense to use it for SCTP as well. This separation should make > future work both on BaseChannel and the SCTP code paths easier. > > SctpDataEngine now becomes SctpTransport, and is used by WebRtcSession > directly. cricket::DataChannel is also renamed, to RtpDataChannel, so it > doesn't get confused with webrtc::DataChannel any more. > > Beyond just moving code around, some consequences of this CL: > - We'll now stop using the worker thread for SCTP. Packets will be > processed right on the network thread instead. > - The SDP directional attribute is ignored, as it's supposed to be. > > BUG=None > > Review-Url: https://codereview.webrtc.org/2564333002 > Cr-Commit-Position: refs/heads/master@{#15906} > Committed: https://chromium.googlesource.com/external/webrtc/+/67b3bbe639645ab719972682359acda303d94454 TBR=pthatcher@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=None Review-Url: https://codereview.webrtc.org/2614813003 Cr-Commit-Position: refs/heads/master@{#15908}
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. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.