Re:I reverse engineered McDonalds’ internal API
by Dylan16807 on Thursday October 22, 2020 @04:14PM
(#24862812)
NTP is fine but so is pulling time off a server header if it's phoning home to report status.
Re:I reverse engineered McDonalds’ internal API
by nitrogen on Thursday October 22, 2020 @05:17PM
(#24863404)
Not that it matters for ice cream, but NTP can compensate for latency better than HTTPx can.
Re:I reverse engineered McDonalds’ internal API
by thisisnico on Friday October 23, 2020 @01:52PM
(#24872039)
It's also easy to implement since it will be integrated into the OS of the ice cream machine already.
Re:I reverse engineered McDonalds’ internal API
by ezconnect on Thursday October 22, 2020 @04:39PM
(#24863061)
GPS based clock is better no need for internet connection. Seiko and other company has been doing this for years.
Re:I reverse engineered McDonalds’ internal API
by marshray on Thursday October 22, 2020 @04:52PM
(#24863174)
NTP is typically backed by GPS.
If you have a datacenter full of computers, obviously you don't want to run a separate GPS antenna for every system. NTP allows systems to synchronize to GPS over a network.
Re:I reverse engineered McDonalds’ internal API
by Scoundreller on Thursday October 22, 2020 @05:07PM
(#24863316)
Need a clear sky connection though.
Don't you mean NTP? We've had this technology for years! If it's connected to the internet, it's a pretty fundamental piece of pretty much any networked OS. You can ensure correct time this way.