Re: [time-nuts] Leap second smear at Google
I don't know how elegant this solution from Google is Christopher, It's a clever, internal solution to the difficult problem leap seconds create in any large automated system. That blog entry is 2 years old. The issue has been discussed at length on the leap second mailing list; you can read the archives, if you have the time. /tvb www.leapsecond.com ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] Leap second smear at Google
Besides the famous Android stint described in Google bug 5485 https://code.google.com/p/android/issues/detail?id=5485 that took 2 years to fix, so many Android phones system clocks were 15 seconds fast then, I just found the source of another discrepancy where Google spreads the leap second offset to avoid artifacts with servers, platforms, environments or programs unable to handle a sudden second leap : http://googleblog.blogspot.com/2011/09/time-technology-and-leaping-seconds.html Maybe not as bad as Oracle in 2009 : http://www.pcworld.com/article/156453/article.html I don't know how elegant this solution from Google is, especially with Google Wallet time payments or transactions that could be back-dated in relation to a banking system, or other Google apps, but I thought it might be of interest to some before they need a house of clocks to keep in sync with Google on such days ! http://www.youtube.com/watch?v=xyRKQ84ztkE Christopher Quarksnow ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Leap second smear at Google
Christopher, Obviously GOOG needs a time-nut on their staff! Interesting stuff! John W. On Fri, Sep 20, 2013 at 6:48 PM, Christopher Quarksnow cquarks...@gmail.com wrote: Besides the famous Android stint described in Google bug 5485 https://code.google.com/p/android/issues/detail?id=5485 that took 2 years to fix, so many Android phones system clocks were 15 seconds fast then, I just found the source of another discrepancy where Google spreads the leap second offset to avoid artifacts with servers, platforms, environments or programs unable to handle a sudden second leap : http://googleblog.blogspot.com/2011/09/time-technology-and-leaping-seconds.html Maybe not as bad as Oracle in 2009 : http://www.pcworld.com/article/156453/article.html I don't know how elegant this solution from Google is, especially with Google Wallet time payments or transactions that could be back-dated in relation to a banking system, or other Google apps, but I thought it might be of interest to some before they need a house of clocks to keep in sync with Google on such days ! http://www.youtube.com/watch?v=xyRKQ84ztkE Christopher Quarksnow ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
