Bug 55542

Summary: [task] Protocol: Format of time values
Product: Wayland Reporter: John Kåre Alsaker <john.kare.alsaker>
Component: waylandAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description John Kåre Alsaker 2012-10-02 13:59:19 UTC 
When it comes to the time values, I'm assuming that the values are simply ticks relative to another point in time. Should there be an event telling client in which point in time all the following values are relative to? This event would be sent when the client connects and when the time value overflows. It could simply handling of time overflows in clients and allow them to convert the values to absolute time.
Comment 1 Pekka Paalanen 2012-10-02 14:12:41 UTC 
No.

Absolute time here is irrelevant. The time is counted from an arbitrary point, monotonically, and only the time difference between events is significant.

This is not meant to be a datetime clock.
Comment 2 John Kåre Alsaker 2012-10-02 14:36:43 UTC 
Informing the client of overflows is still required for it to compute the time difference between two events.
Comment 3 Kristian Høgsberg 2012-10-02 15:05:18 UTC 
(In reply to comment #2)
> Informing the client of overflows is still required for it to compute the
> time difference between two events.

No, that's why the time values are uint.  The overflow behavior for unsigned integers is well-defined and gives you the delta.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.