Re: [ws-rx] DA and Protocol: is the date over?

[Dan Leshchiner <dleshc@tibco.com>]

we kept encountering time jumping around and wreaking havoc on our 
timers situations over and over until we put some code in to protect 
against it. in any case, there is always administrative action and 
reboot with no persistent clock situations to deal with.

Rich Salz wrote:

>> because time can go backwards (at least once a year
>
>
> You mean daylight savings ("summer") time?  That doesn't count, it's 
> just the local representation of the "real" time, which is UTC. Time 
> is monotonically increasing, as long as the bad guys don't get in.
>
>     /r$
>