darkdust/mhsntp

SNTP client library for macOS, iOS and tvOS.

mhsntp's Issues

Manager should give feedback about whether querying failed.

Right now, there is no way to tell whether querying the time offsets has failed for all servers (for example, because the network is down). This might be useful information.

Maybe a state property might be useful for this. It would also help solve a use-case of #1: waiting for the first responses to arrive.

Improve unit test helper methods

Right now in ClientTests.swift, when an assertion is triggered in runLocalServerTest or runLocalServerTestKiss, it's not obvious which call to these methods failed. This should be improved.

Add manycast support

Support for servers in manycast most. See RFC 4330 §2 for a description.

Add broadcast support

Support for servers in broadcast most. See RFC 4330 §2 for a description.

Users Messing With the System Clock

Hey, I found by way here (and by the way, thanks for MHSNTP!) researching / planning a solution to user interference with the system clock.

In that stead, I think instead of using [NSDate date] to keep track of relative time....

(for example...
- (void)locked_query:(MHSNTPManagerEntry *)entry
entry.lastRequestDate = [NSDate date];
)

that it would be better to use this method of calculating system uptime

Post notification on time offset change

The MHSNTPManager should probably post a notification once the calculated time offset has changed. This comes at a little cost and I'm not sure whether it's needed at all. Need to come up with a use-case first.