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?
Thread beginning with comment 474813
To read all comments associated with this story, please click here.
by Nelson on Fri 27th May 2011 13:55 UTC
Member since:

Been doing it in Silverlight for years. Blocking calls are pretty ancient by any modern developers standards.

Is there some added complexity? Yeah. Do you lose some finer control over execution flow? Probably. But its really nothing a few signals cant fix.

You gain a lot more in scalability though.

Reply Score: 2

RE: Yes.
by JAlexoid on Fri 27th May 2011 15:52 in reply to "Yes."
JAlexoid Member since:

Blocking calls are still quite common. Just because on the very next line you know you have the data or an error/exception. Mostly blocking API is non-blocking API wrapped and synched to the response.

Edited 2011-05-27 15:52 UTC

Reply Parent Score: 2