"unruh" <[email protected]> wrote in message news:[email protected]... > On 2013-01-26, [email protected] <[email protected]> wrote:
>> [...] I obviously don't want to hard-code for a specific time server >> because things could change after the user gets my app and it is >> unfair to send a whole block of users to the same server. The >> Server Pool looks promising. Does pool.ntp.org just behave like a >> Stratum 2 server so I could hard-code that URL into my implementation >> of NTP in my app? ... [...] > And no you definitely should not hard code a site, unless it is one > controlled by you. [...] > Note pool.ntp.org does NOT have an IP-- each dns request gives a > different IP, so you need the name, not an IP. Which is exactly why hardcoding pool.ntp.org _is_ allowable, in my opinion - and in fact indicated in such a case as this. Exactly because (as I suspect you meant) it is not a fixed site, but a symbolic name that translates to some reasonable site that is available now. Incidentally, to the OP, it's not a URL. It is a DNS name. Groetjes, Maarten Wiltink _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
