35c5cc8a6f
DSCP is controlled by the spec-compliant API RTCRtpEncodingParameters.networkPriority[1]. It already has a default value that is the same as when DSCP is disabled. - If you want non-default DSCP default values, you need to set networkPriority and shouldn't need to set a non-standard googDscp flag for it to have an effect. - If you want the default DSCP value, you wouldn't change networkPriority and so you don't care if enable_dscp is true... you'll get the default regardless. Drive-by: This CL also adds crbug references to other goog flags. [1] https://w3c.github.io/webrtc-priority/#dom-rtcrtpencodingparameters-networkpriority Bug: chromium:1315574 Change-Id: I15a0470fa04f55e2534cee0d240eeb03446c2de6 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/258940 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/main@{#36550}
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.