W3C home > Mailing lists > Public > public-web-perf@w3.org > March 2012

[HighResolutionTime] accuracy

From: Jannis Froese <froese@lionservers.de>
Date: Fri, 23 Mar 2012 00:36:11 +0100
To: <public-web-perf@w3.org>
Message-ID: <88bbcc89105adcd453d68f0541400dcb@lionservers.de>
 I am a java script developer and always like to follow the latest

 The monotonic clock introduced by High Resolution Time is a huge step
 forward and will eliminate many problems.

 The higher accuracy however is in many situations worthless if you 
 know how accurate it really is. You can't define a reaction based on a
 delay of for example more than a a twentieth of a millisecond if it 
 guaranteed that the clock is that accurate. Thus High Resolution Time 
 is in
 many situations only usable up to the guaranteed accuracy of a tenth of 

 Therefore I would propose to include an additional value stating the 
 accuracy which the client can deliver. This would add flexibility and
 remove unnecessary restrictions, particularly when the delivered 
 improves as hardware improves.


 Jannis Froese
Received on Saturday, 24 March 2012 00:18:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:01:11 UTC