commit | 907abe44116391fdd8d779f6765aead155fc20a3 | [log] [tgz] |
---|---|---|
author | deadbeef <deadbeef@webrtc.org> | Thu Aug 04 19:22:18 2016 |
committer | Commit bot <commit-bot@chromium.org> | Thu Aug 04 19:22:22 2016 |
tree | 714b1640e5761f447925db852fcf6b2609620e79 | |
parent | e7db69bc3cbdf7f72f90731df318af34a28f5331 [diff] |
Revert of Modified PeerConnection and WebRtcSession for end-to-end QuicDataChannel usage. (patchset #8 id:280001 of https://codereview.webrtc.org/2166873002/ ) Reason for revert: Reverting because it broke an RTP data channel test on the FYI bots. Original issue's description: > Modified PeerConnection and WebRtcSession 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 ben modified to use a QuicDataTransport > instead of a DtlsTransportChannelWrapper/DataChannel > when QUIC should be used > > QuicDataTransport implements the generic functions of > BaseChannel to manage the QuicTransportChannel. > > Committed: https://crrev.com/34b54c36a533dadb6ceb70795119194e6f530ef5 > Cr-Commit-Position: refs/heads/master@{#13645} 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/2206793007 Cr-Commit-Position: refs/heads/master@{#13647}
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.