Bug
Opened this issue · 2 comments
When [NetworkClock sharedNetworkClock] is first called when there is no internet connection, no network associations will be created, meaning that no timers are ever created, so even when internet is back on at a later point in time, nothing will happen / no pings to any time servers will happen.
I'd be interested in other users' opinions on this.
Mine is that determining the presence of network connectivity is not the responsibility of NTP. While ios-ntp is a severely cut down version of the canonical NTP code and already makes exceptions (and could make this one), I'm reluctant to move this far away the core time protocol function.
I'm trying to prevent clock-cheating using ios-ntp so I appreciate anything that makes ios-ntp a smarter, reliable clock aware of it's "surroundings". That said I don't know much about the NTP standard itself.