Re: Python recompile

On 3/11/2025 3:56 PM, Lawrence D'Oliveiro wrote:

On Tue, 11 Mar 2025 14:12:01 -0700, Chris M. Thomasson wrote:
 

A "traditional" server loop would block on IOCP (aka INFINITE).

 A traditional server loop (I’ve written a few) would block on one of a
number of possible conditions occurring, e.g.
      * A new client connection coming in
     * A new request received on a client connection
     * A response ready to go out on a client connection
     * A timeout of a client connection due to inactivity
     * Some periodic housekeeping task needing to be performed
 You want things to be nondeterministic: the server loop should be able to
respond immediately to the first event that comes in from whatever source,
not based on some arbitrary ordering of entries in an array to a poll(2)-
style call.
 

Also, waiting for say 5 minutes for IO and timing out so the server
loop in the worker threads can examine other things can be
beneficial as well.

 It would be more efficient to have the timeout equal to the due time of
the earliest timed task needing attention.

Have you ever used IOCP before? You block on it and it wakes up when an io event occurred. This can be accepting a new connection, connecting to another socket, receiving or sending data, ect... The timeout, try, is useful in certain scenarios, but blocking on IOCP for INFINITE is fine. You can try to connect to x, then IOCP will tell you when that connection is done, or error, whatever. You can get a new connection, IOCP will tell you what that occurs. You can finish sending some data, IOCP will tell you that that is done. You get some receive some data, again , IOCP handles it. Just block on it and examine its return status and act accordingly.