Remove enable_rtp_data_channel
This denies the ability to request RTP data channels to callers. Later CLs will rip out the actual code for creating these channels. Bug: chromium:928706 Change-Id: Ibb54197f192f567984a348f1539c26be120903f0 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/177901 Reviewed-by: Henrik Boström <hbos@webrtc.org> Commit-Queue: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33740}
This commit is contained in:

committed by
Commit Bot

parent
fa8a9465d5
commit
bc959b61b3
@ -404,12 +404,6 @@ class RTC_EXPORT PeerConnectionInterface : public rtc::RefCountInterface {
|
||||
// from consideration for gathering ICE candidates.
|
||||
bool disable_link_local_networks = false;
|
||||
|
||||
// If set to true, use RTP data channels instead of SCTP.
|
||||
// TODO(deadbeef): Remove this. We no longer commit to supporting RTP data
|
||||
// channels, though some applications are still working on moving off of
|
||||
// them.
|
||||
bool enable_rtp_data_channel = false;
|
||||
|
||||
// Minimum bitrate at which screencast video tracks will be encoded at.
|
||||
// This means adding padding bits up to this bitrate, which can help
|
||||
// when switching from a static scene to one with motion.
|
||||
|
Reference in New Issue
Block a user