Thanks, but I will use this as a last resort, what I am really interested in is an exposed webservice.
–
JLJul 28 '09 at 11:51

8

Synching time over a webservice seems like a tremendously bad idea. NTP is a well established protocol that was specifically developed to deliver accurate results.
–
innaMJul 28 '09 at 12:07

1

This is exactly what NTP is for. You send it a request via UDP and receive a response with time information. It's an old, reliable and robust protocol and most NTP servers have very high availability. In addition to that, you can query multiple NTP servers in case 1 is down.
–
Tommy CarlierJul 28 '09 at 12:08

1

Moreover, if NTP could suffer about network latency, imagine a webservice request with all that SOAP glory
–
HyLianJul 28 '09 at 12:25

So... this exact Pool.ntp.org/zone - this is the right server to use?
–
JLJul 28 '09 at 12:56

www.pool.ntp.org is a web page that guides you through which pool of servers you should use (which is closer to you). The NTP pool contains large number of servers, so it's very unlikely that you'll stumble upon on a non-working server; very recommended. HTTP will never deliver precise time like NTP.