On Apr 10, 2:20 pm, Paul Rubin <http://[EMAIL PROTECTED]> wrote:
> "Godzilla" <[EMAIL PROTECTED]> writes:
> > After the time sync, say 15 seconds backward, the thread is sitting on
> > that get() method for a total of 17 seconds. We can only sync the
> > device once per day and the time can drift up to 15 seconds per day!!
>
> Try to avoid syncing lke that.  System clocks drift but the drift
> rates tend to be constant, so there are schemes for gradually slowing
> down or speeding up the system clock in order to keep it synchronized
> with an external reference.
>
> > Anyone knows a solution to this problem or an alternative method?
>
> http://www.ntp.org

Hi Paul,

Ok... But I'm afraid no syncing is not an option for the device...

-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to