b59e9045bf
The timestamps returned by the clocks do not have an epoch. Each clock should be able to convert a timestamp it returns to an NTP time. The default implementation for querying for an NTP time is converting the current timestamp. This is favored over returning the offset between the relative and the NTP time because there is a field trial that makes the real clock revert to using system dependent methods for getting the NTP time. Bug: webrtc:11327 Change-Id: Ia139b2744b407cae94420bf9112212ec577efb16 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/219687 Reviewed-by: Minyue Li <minyue@webrtc.org> Reviewed-by: Niels Moller <nisse@webrtc.org> Commit-Queue: Paul Hallak <phallak@google.com> Cr-Commit-Position: refs/heads/master@{#34071}
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