Add flag to use datagram transport (without implementation)

Integration with datagram transport will come in next CLs.

NOTE that since we now have implemented negotiation for media transport, we can replace configuration flags with field trials, but it will be done later for both media and datagram transports.

Bug: webrtc:9719
Change-Id: Icf062d030899d53d5646977ba195d1634050704b
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/137820
Commit-Queue: Anton Sukhanov <sukhanov@webrtc.org>
Reviewed-by: Steve Anton <steveanton@webrtc.org>
Reviewed-by: Bjorn Mellem <mellem@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#27996}
This commit is contained in:
Anton Sukhanov 2019-05-20 14:39:06 -07:00 committed by Commit Bot
parent 9f864be38a
commit 762076b886

View File

@ -615,6 +615,16 @@ class RTC_EXPORT PeerConnectionInterface : public rtc::RefCountInterface {
// |enable_rtp_data_channel| is invalid.
bool use_media_transport_for_data_channels = false;
// If MediaTransportFactory is provided in PeerConnectionFactory, this flag
// informs PeerConnection that it should use the DatagramTransportInterface
// for packets instead DTLS. It's invalid to set it to |true| if the
// MediaTransportFactory wasn't provided.
//
// TODO(sukhanov): Once we have a working mechanism for negotiating media
// transport through SDP, we replace media transport flags in
// RTCConfiguration with field trials.
bool use_datagram_transport = false;
// Defines advanced optional cryptographic settings related to SRTP and
// frame encryption for native WebRTC. Setting this will overwrite any
// settings set in PeerConnectionFactory (which is deprecated).