Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: "Chris M. Thomasson" Newsgroups: comp.lang.c Subject: Re: Python recompile Date: Mon, 10 Mar 2025 21:25:21 -0700 Organization: A noiseless patient Spider Lines: 26 Message-ID: References: <20250304092827.708@kylheku.com> <871pv861ht.fsf@nosuchdomain.example.com> <20250308192940.00001351@yahoo.com> <20250309012626.00001276@yahoo.com> <20250309112807.0000489d@yahoo.com> <20250310152000.00004955@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Tue, 11 Mar 2025 05:25:23 +0100 (CET) Injection-Info: dont-email.me; posting-host="77500da324fcce57a578074132fa14ab"; logging-data="1912498"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18wfWUbY1eaAvrJHtOjNHpuRJlzt1mWnEU=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:/WNrkcKl0NIiNkWj/XLMal262P8= In-Reply-To: Content-Language: en-US Bytes: 3287 On 3/10/2025 8:07 PM, Lawrence D'Oliveiro wrote: > On Mon, 10 Mar 2025 17:56:03 -0700, Chris M. Thomasson wrote: > >> On 3/10/2025 4:19 PM, Lawrence D'Oliveiro wrote: >> >>> On Mon, 10 Mar 2025 14:40:23 -0700, Chris M. Thomasson wrote: >>> >>>> For some damn reason I am remembering that the array that >>>> WaitForMultipleObjects waits on should be "shifted" or even randomized >>>> per call in a server loop that is using EVENTS. IIRC, this was way >>>> back in late 90's and early 2000's. >>> >>> I would hope that the order of entries is not important, as that would >>> defeat the point of non-determinism. >> >> I remember reading a paper on the 50,000 concurrent connections issue >> wrt IOCP vs events. Well, it made sure to tell the user to at least >> shift the array that WFMO's waits on, per call in the server loop. > > But why? Surely events relevant to entries in the list should be serviced > in the order they arrive, not in the order in which the entries happen to > occur in the list. There is no other reasonable way to do it. Well, it just the way WFMO is implemented. Notice that post from Kaz wrt the index... I remember reading about it is more than one place now, for some damn reason. NT insider comes to mind.