[Python-ideas] An alternate approach to async IO
sturla at molden.no
Wed Nov 28 19:57:32 CET 2012
On 28.11.2012 16:59, Guido van Rossum wrote:
> OK, now I see. (I thought that was how everyone was using IOCP.
> Apparently not?) However, the "short busy wait" worries me. What if
> your app *doesn't* get a lot of requests?
Then there would be no busy wait.
> Isn't the alternative to have a "thread pool" with just one thread,
> which runs all the Python code and gets woken up by IOCP when it is
> idle and there is a new event? How is Trent's proposal an improvement?
I'm not sure.
This is what I suggested in my previous mail.
More information about the Python-ideas