| commit | ada810aab20777abca892c2a523d3aa47f03b692 | [log] [tgz] |
|---|---|---|
| author | Björn Terelius <terelius@webrtc.org> | Mon May 24 08:19:55 2021 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 17 12:08:54 2021 |
| tree | 78f3dcbd999bc00409883dc483209653e068e12f | |
| parent | 1bb36d2c776dbd17cbbe1a4fdd69ccc7e2190183 [diff] |
Reland "Deprecate microsecond timestamps in RTC event log." This is a reland of e6ee8fab7eac915b2b6abc9b71b6d33ad086f3d1 Original change's description: > Deprecate microsecond timestamps in RTC event log. > > (Microsecond timestamps are only used in the legacy wire-format, > and the clocks only have microsecond resolution on some platforms.) > > Also convert structs on the parsing side to use a Timestamp instead > of a uint64_t to represent the log time. > > Bug: webrtc:11933 > Change-Id: Ide5a0217d99f13f2e243115b163f13e0525648c7 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/219467 > Commit-Queue: Björn Terelius <terelius@webrtc.org> > Reviewed-by: Christoffer Rodbro <crodbro@webrtc.org> > Reviewed-by: Sebastian Jansson <srte@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#34097} Bug: webrtc:11933 Change-Id: I295be966ee96b50719ceb4690dad7e7ce958dbac Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/221361 Commit-Queue: Björn Terelius <terelius@webrtc.org> Reviewed-by: Sebastian Jansson <srte@webrtc.org> Reviewed-by: Christoffer Rodbro <crodbro@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34321}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.