51b93a5417
When a timer expires, it can optionally return a new expiration value. Clearly, that value can't be zero, as that would make it expire immediately again. To simplify the interface, and make it easier to migrate to rtc::TimeDelta, change it from an optional value to an always-present value that - if zero - means that the expiration time should be unchanged. This is just an internal refactoring, and not part of any external interface. Bug: webrtc:15593 Change-Id: I6e7010d2dbe774ccb260e14fd6b9861c319e2411 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/325281 Commit-Queue: Victor Boivie <boivie@webrtc.org> Reviewed-by: Florent Castelli <orphis@webrtc.org> Cr-Commit-Position: refs/heads/main@{#41045}
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 here 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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation