Hi, > > I would prefer an option that gets the time ether from > currentTimeMillis() or from nanoTime(). On windows, the latter gets > its value from the QueryPerformanceCounter() API which causes the > drift from the system-clock. >
On few particular machines we have seen a drift that is very extreme and it showed that nanoTime() did not give correct elapsed times too. Therefor in our case, we strongly prefer an option that switches of nanoTime() completely and use currentTimeMillis() instead, for timestamps and also for elapsed time calculation. Such an option would be very much appreciated. Also, we rely on the system-clock for comparison with other tools such as tcpdump, therefore we really need an implementation based on currentTimeMillis() only. Best regards, Andrej --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
