Reason for revert: Reverting because description was inaccurate. Will reland after updating description. Original issue's description: > Modify PeerConnection for end-to-end QuicDataChannel usage > > To allow end-to-end QuicDataChannel usage with a > PeerConnection, RTCConfiguration has been modified to > include a boolean for whether to do QUIC, since negotiation of > QUIC is not implemented. If one peer does QUIC, then it will be > assumed that the other peer must do QUIC or the connection > will fail. > > PeerConnection has been modified to create data channels of type > QuicDataChannel when the peer wants to do QUIC. > > WebRtcSession has been modified to use a QuicTransportChannel > instead of a DtlsTransportChannelWrapper/DataChannel > when QUIC should be used. > > Modification of previous in-flight CL: https://codereview.chromium.org/1844803002/ > > Committed: https://crrev.com/36c8d69ce188102ae6fd48c371cf1518f08698fb > Cr-Commit-Position: refs/heads/master@{#13470} TBR=pthatcher@webrtc.org,zhihuang@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true Review-Url: https://codereview.webrtc.org/2146133002 Cr-Commit-Position: refs/heads/master@{#13471}
Revert of Delete method cricket::VideoFrame::Copy. (patchset #7 id:120001 of https://codereview.webrtc.org/2080253002/ )
Revert of Modify PeerConnection for end-to-end QuicDataChannel usage (patchset #4 id:60001 of https://codereview.webrtc.org/2089553002/ )
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.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://chromium.googlesource.com/external/webrtc
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
Description
The idea is to make CMake build for WebRTC m130 version - for audio processing module
Languages
C++
90.3%
Java
2.9%
C
2.2%
Objective-C++
2%
Python
1.3%
Other
1%