50b95525c7
This is a partial revert of commit f9e502d935fa9ca8d9cc7540680021b93d285f28. Reason for revert: Functionality turns out to be needed by some partners for some months more. Original change's description: > Remove enable_dtls_srtp option > > This is part of the removal of support for SDES. > > Bug: webrtc:11066 > Change-Id: I448d0e0032672c04c87b00550ab4b9d792071a0b > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/234864 > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Commit-Queue: Harald Alvestrand <hta@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#35262} # Not skipping CQ checks because original CL landed > 1 day ago. Bug: webrtc:11066, chromium:1271469 Change-Id: I79a90f025e53816789b391bc52a0e896b9be87e1 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/238170 Reviewed-by: Henrik Boström <hbos@webrtc.org> Commit-Queue: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35378}
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.