| |||||||||||||
Leaping seconds and looping serversLeaping seconds and looping serversPosted Jul 5, 2012 4:53 UTC (Thu) by raven667 (subscriber, #5198)In reply to: Leaping seconds and looping servers by wahern Parent article: Leaping seconds and looping servers
How about we use GUIDs and distribute copies of the official list that uniquely identifies every second past or future.
8-) kidding of course.
(Log in to post comments)
Leaping seconds and looping servers Posted Jul 12, 2012 13:41 UTC (Thu) by njs (guest, #40338) [Link]
Well. Except. It turns out that to get a really precise TAI timestamp, what you do is:
1) When the event occurs, get a timestamp from the nearest convenient national lab atomic clock.
2) Wait a few weeks while the different national labs compare their clock's relative drift rates over the last period, pick some sort of average as the "real TAI time", and publish tables mapping from what their clock actually did to this consensus clock that doesn't exist.
3) Look up the timestamp you got in step 1 in this table.
It's hard to make jokes about time...
|
|||||||||||||