7da4e563b7
Adds a field trial and configuration parameter to control whether datagram transport may be used for data channels in a receive-only manner. By default, if use_datagram_transport_for_data_channels is enabled, PeerConnection will create a datagram transport and offer its use for outgoing calls as well as accept incoming offers with compatible datagram transport parameters. With this change, a receive_only mode is added for datagram transport data channels. When receive_only is set, the PeerConnection will not create or offer datagram transports for outgoing calls, but will accept incoming calls that offer compatible datagram transport parameters. Bug: webrtc:9719 Change-Id: I35667bcc408ea4bbc61155898e6d2472dd262711 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/154463 Reviewed-by: Seth Hampson <shampson@webrtc.org> Commit-Queue: Bjorn Mellem <mellem@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29327}
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.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- 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
- Coding style guide
- Code of conduct