619b29423c
RtpSender uses a transactional model when getting and setting RtpParameters. One must call GetParameters() and then can use the returned object in a subsequent call to SetParameters(). PeerConnection was calling GetParameters() and SetParameters() during negotiation in SetLocalDescription and SetRemoteDescription effectively invalidating any parameters that the client previously held. This change introduces an internal way for the platform to modify parameters without invalidating the transactional model, provided that the modification is not severe. Ex. removing simulcast layers is a severe modification and will invalidate any outstanding parameters. Bug: webrtc:10339 Change-Id: I362e8ca4d9556e04a1aa7a3e74e2c275f8d16fbc Reviewed-on: https://webrtc-review.googlesource.com/c/124504 Reviewed-by: Seth Hampson <shampson@webrtc.org> Reviewed-by: Steve Anton <steveanton@webrtc.org> Commit-Queue: Amit Hilbuch <amithi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26864}
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