Linked by Hadrien Grasland on Fri 27th May 2011 11:34 UTC
General Development After having an interesting discussion with Brendan on the topic of deadlocks in threaded and asynchronous event handling systems (see the comments on this blog post), I just had something to ask to the developers on OSnews: could you live without blocking API calls? Could you work with APIs where lengthy tasks like writing to a file, sending a signal, doing network I/O, etc is done in a nonblocking fashion, with only callbacks as a mechanism to return results and notify your software when an operation is done?
Permalink for comment 474834
To read all comments associated with this story, please click here.
RE: IO calls never need to block.
by JAlexoid on Fri 27th May 2011 16:00 UTC in reply to "IO calls never need to block."
JAlexoid
Member since:
2009-05-19

If it's on another thread then that is not in the same call stack, is it? Otherwise that problem has been successfully mitigated using reentrant mutexes, such as used in Java.
But the problem is really bad where you use sub-threads that access a shared resource.

Reply Parent Score: 2