Yeah, I remember the days before the pool was created. Back then the best solution was to hand pick few local time servers from closest universities and such, www.pool.ntp.org makes it much easier. I don't know where are you going with this NTPUDPClient.java client but I think it's better to run ntp daemon on your system and query your OS clock. During normal operation ntpd keeps track of the time on few different servers ( around 5 on my system). It monitors these servers and tries to determine which one provides the best time based on network latency and other factors. Now, I don't know how NTPUDPClient.java works, but if it doesn't take network latencty into account and is not picky about the server it is connected to then it probably it is far from accurate.
On Aug 22, 9:35 pm, nonlinear5 <[email protected]> wrote: > > I don't believe that any time server would allow you to check the time > > that often, it would probably consider it as a DoS attack or some > > sort of abuse. > > There seems to be a way around this. Instead of a particular time > server, you can specify an NTP server pool. Some of these pools > contain literally thousands of time servers, and they use "round > robin" to select a server when you request time. So, you can request > time multiple times per second without hitting any particular server > too often. I am using Apache NTPUDPClient.java to get time every 100 > milliseconds, and it seems to be running smoothly. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en -~----------~----~----~----~------~----~------~--~---
