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}
How to write code in the api/ directory
Mostly, just follow the regular style guide, but:
- Note that
api/code is not exempt from the “.hand.ccfiles come in pairs” rule, so if you declare something inapi/path/to/foo.h, it should be defined inapi/path/to/foo.cc. - Headers in
api/should, if possible, not#includeheaders outsideapi/. It’s not always possible to avoid this, but be aware that it adds to a small mountain of technical debt that we’re trying to shrink. .ccfiles inapi/, on the other hand, are free to#includeheaders outsideapi/.
That is, the preferred way for api/ code to access non-api/ code is to call
it from a .cc file, so that users of our API headers won’t transitively
#include non-public headers.
For headers in api/ that need to refer to non-public types, forward
declarations are often a lesser evil than including non-public header files. The
usual rules still apply, though.
.cc files in api/ should preferably be kept reasonably small. If a
substantial implementation is needed, consider putting it with our non-public
code, and just call it from the api/ .cc file.