Remove QUIC transport/data channel
Originally, the idea was to implement QUIC data channels as a PeerConnection API. Now, the effort has shifted to implementing it as a part of ORTC which will live in Chromium. Since this code has not been maintained and is not currently being used, remove it to reduce maintenance overhead while a copy will be retained in the Git history. Bug: webrtc:8385 Change-Id: I2719c007a0de0118b67d41a425f900b66c52f65a Reviewed-on: https://webrtc-review.googlesource.com/14100 Reviewed-by: Patrik Höglund <phoglund@webrtc.org> Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> Reviewed-by: Zhi Huang <zhihuang@webrtc.org> Commit-Queue: Steve Anton <steveanton@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20412}
This commit is contained in:
@ -436,11 +436,6 @@ class PeerConnectionInterface : public rtc::RefCountInterface {
|
||||
|
||||
struct cricket::MediaConfig media_config;
|
||||
|
||||
// This doesn't currently work. For a while we were working on adding QUIC
|
||||
// data channel support to PeerConnection, but decided on a different
|
||||
// approach, and that code hasn't been updated for a while.
|
||||
bool enable_quic = false;
|
||||
|
||||
// If set to true, only one preferred TURN allocation will be used per
|
||||
// network interface. UDP is preferred over TCP and IPv6 over IPv4. This
|
||||
// can be used to cut down on the number of candidate pairings.
|
||||
@ -469,7 +464,6 @@ class PeerConnectionInterface : public rtc::RefCountInterface {
|
||||
// (STUN pings), in milliseconds.
|
||||
rtc::Optional<int> ice_check_min_interval;
|
||||
|
||||
|
||||
// ICE Periodic Regathering
|
||||
// If set, WebRTC will periodically create and propose candidates without
|
||||
// starting a new ICE generation. The regathering happens continuously with
|
||||
|
||||
Reference in New Issue
Block a user