Re: Queue get timeout parameter question

Godzilla> Ok... But I'm afraid no syncing is not an option for the Godzilla> device... Then you'll either need to use something like ntp or sync much more frequently so you don't yank the time by so much. Skip -- http://mail.python.org/mailman/listinfo/python-list

Re: Queue get timeout parameter question

On Apr 10, 5:38 pm, Thomas Krüger <[EMAIL PROTECTED]> wrote: > Godzilla schrieb: > > > > > > > I have been using the queue module for a multithreaded environment and > > things seem to work well... until we had a requirement for the > > application to be able to time sync to the server. With the ti

Re: Queue get timeout parameter question

Godzilla schrieb: > I have been using the queue module for a multithreaded environment and > things seem to work well... until we had a requirement for the > application to be able to time sync to the server. With the time sync, > it actually disorientated the timeout in the queue's get() method...

Re: Queue get timeout parameter question

On Apr 10, 2:20 pm, Paul Rubin 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 u

Re: Queue get timeout parameter question

"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

Queue get timeout parameter question

Dear all, I have been using the queue module for a multithreaded environment and things seem to work well... until we had a requirement for the application to be able to time sync to the server. With the time sync, it actually disorientated the timeout in the queue's get() method... e.g. get(item