commit | ac2f3d14e45398930bc35ff05ed7a3b9b617d328 | [log] [tgz] |
---|---|---|
author | Benjamin Wright <benwright@webrtc.org> | Thu Oct 11 00:21:08 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Oct 11 19:14:42 2018 |
tree | 23bb4aab6150ea8ce63b46e80b46c03a342017ed | |
parent | 8285841e8f3f077702f6fae66621083edccb83f7 [diff] |
Move CryptoOptions to api/crypto from rtc_base/sslstreamadapter.h Promotes rtc::CryptoOptions to webrtc::CryptoOptions converting it from class that only handles SRTP configuration to a more generic structure that can be used and extended for all per peer connection CryptoOptions that can be on a given PeerConnection. Now all SRTP related options are under webrtc::CryptoOptions::Srtp and can be accessed as crypto_options.srtp.whatever_option_name. This is more inline with other structures we have in WebRTC such as VideoConfig. As additional features are added over time this will allow the structure to remain compartmentalized and concerned components can only request a subset of the overall configuration structure e.g: void MySrtpFunction(const webrtc::CryptoOptions::Srtp& srtp_config); In addition to this it made little sense for sslstreamadapter.h to hold all Srtp related configuration options. The header has become loo large and takes on too many responsibilities and spilting this up will lead to more maintainable code going forward. This will be used in a future CL to enable configuration options for the newly supported Frame Crypto. Change-Id: I99d1be36740c59548c8e62db52d68d738649707f Bug: webrtc:9681 Reviewed-on: https://webrtc-review.googlesource.com/c/105180 Reviewed-by: Emad Omara <emadomara@webrtc.org> Reviewed-by: Kári Helgason <kthelgason@webrtc.org> Reviewed-by: Sami Kalliomäki <sakal@webrtc.org> Reviewed-by: Qingsi Wang <qingsi@webrtc.org> Reviewed-by: Steve Anton <steveanton@webrtc.org> Commit-Queue: Benjamin Wright <benwright@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25130}
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.
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.