>> Spawning a process just to learn if a socket is blocking? Wow. >> >> Sounds like caching the information independently (like we already do >> for dirfd) is the way to go then, so that we only have to spawn when >> inheriting sockets through stdin/out/err. > > > That is the idea.... But at least we know is a socket is blocking or not
Another idea is to use thread and suspendthread to stop the call it seems that it will work but ake care of problem mentionned here: http://stackoverflow.com/questions/3444190/windows-suspendthread-doesnt-getthreadcontext-fails > Another one is to use > http://www.codeproject.com/KB/threads/QueueUserAPCEx_v2.aspx > > Bastien > > Bastien >
