System.Time.Clock Design Issues

[Aaron Denney]

On 2005-02-04, Ashley Yakeley <ashley at semantic.org> wrote:
> In article <42035F4E.6000104 at imperial.ac.uk>,
>  Keean Schupke <k.schupke at imperial.ac.uk> wrote:
>
>> SO in effect what you are saying is that system time is likely to be
>> neither TAI nor UTC (as hand setting a clock has a greater than 1 second
>> error usually, a non-networked machine will never tell the right time (and
>> even a stopped clock tells the right time twice a day!).
>
> Can we make that assumption? There might be ways of keeping the clock 
> accurate that don't involve TCP/IP.

Right.  The NTP source code has plenty of other things that can by
synced off of, including many fairly common GPS receivers, and radio
clocks.

-- 
Aaron Denney
-><-