Re: Python recompile

On 3/14/2025 4:03 PM, Lawrence D'Oliveiro wrote:

On Fri, 14 Mar 2025 15:06:47 -0700, Chris M. Thomasson wrote:
 

On 3/14/2025 2:20 PM, Lawrence D'Oliveiro wrote:
>

Does that require explicitly queuing a read or a write operation?

>
Well, I still don't know how Python is implementing things.

 The question is, how do *you* think they should be implemented, in such a
way that those claimed limitations would not exist?

I would need to study up on the Python way of implementing these under the hood. Python using ICOP, vs Python using AIO or something. God knows what they have done. As to their limitations, I never worked with Python async io, so I don't know. I know the way I use IOCP over on windows is fine.

Keep in mind that successful IOCP means the completion of an io action
has occurred, or an error has been raised. It could be a new connection,
a buffer was sent, data has been read. That is the C (completion) in
IOCP, see?

 In other words, you actually have to have queued I/O operations
outstanding on every connection in order to use IOCP. Dave Cutler
basically reinvented VMS-style programming, with completion callbacks, in
a slightly more message-based form.
 

If you want to receive data, you queue a receive. When it completes its either successful or its not. Deal with it accordingly. If you want to connect, queue a connect. When its completed its either successful or not, ect, for accept, ect...

This kind of thing does not scale to having thousands of connections open
at once.

Yawn. Of course it does! 50,000 concurrent connections way back in early 2000's. What the heck are you even talking about? ;^o Argh!