devel  

Re: Wrong order of a timeouts processing in WaitForSomething.

David Dawes
Sun, 21 Sep 2003 06:11:13 -0700

On Sat, Sep 20, 2003 at 09:44:19PM -0700, Keith Packard wrote:
>Around 20 o'clock on Sep 20, Ivan Pascal wrote:
>
>> The solution is obvious.  WaitForSomething should not run any callbacks before
>> the Select but just check timers and if there are expired timers call select
>> with a zero timeout.  Also the code before the select checks screensaver and
>> DPMS timeouts.
>
>One use for timeouts is to handle external network events, such as font 
>server reconnect or XDMCP messages.  In those cases, the timeout routine 
>can modify which sockets will be needed in the select mask, hence the 
>desire for the timeout routine to execute before the select (and various 
>BlockHandler) routines are invoked.  When the timeout routine fires only 

I don't see anything in the current code where timers are installed for
XDMCP or font server handling.  They modify the select mask (and timeout)
in their BlockHandlers.

David
-- 
David Dawes                                     X-Oz Technologies
www.XFree86.org/~dawes                          www.x-oz.com
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel