12 ms·
Simple. Measure the latency, and then correct for it! > When a user connects to www.time.gov on a computer or mobile device, the Javascript in the client's br
by kube-system 7y ago
Simple. Measure the latency, and then correct for it!
> When a user connects to www.time.gov on a computer or mobile device, the Javascript in the client's browser checks the local clock on the device and then requests the time from a NIST server, which has been synchronized with UTC(NIST). When the packets containing the NIST time stamp arrive at the client's browser, the device clock is checked again and compared to the first check of the local clock. The result is a measurement the round-trip delay of requesting/receiving the time stamp.
https://www.nist.gov/pml/time-and-frequency-division/about-timegov https://www.nist.gov/pml/time-and-frequency-division/about-t...
- StringyBob 7y ago> It is estimated that the one-half of the round-trip delay happens in each direction. Anyone know how true this is? Particularly for mobile/asymmetric bandwidth connections - what might the errors bars be?