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 474816
To read all comments associated with this story, please click here.
Comment by Mystilleef
by Mystilleef on Fri 27th May 2011 14:06 UTC
Member since:

That's the only way things ever work properly in the real world, asynchronous event-based message-passing systems. I don't ever use blocking calls. I always opt for non-blocking calls. If anything, it forces me to write robust code.

I've noticed the wild assumptions programmers make when writing code based on blocking calls is monumental. The obvious dangerous assumption is that the call will complete successfully, if at all! That's where the cards begin to fall because if that call does not complete, for 10 million and 1 possible reasons, your program just hung indefinitely or crashed.

I learned the hard way. Anyone, who has done any kind of desktop application development probably has an endless list of war stories about the perils of blocking calls.

However, I know many developers (usually with a background in web development) who hate callback based programming. They claim it's hard to understand.

Reply Score: 2