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 474908
To read all comments associated with this story, please click here.
RE[2]: Callback fragmentation
by ndrw on Sun 29th May 2011 04:36 UTC in reply to "RE: Callback fragmentation"
Member since:

Well, that's a simple MVC pattern at work, which is also a kind of an asynchronous framework. I wouldn't call it a bad programming practice, quite the opposite. It does what it is designed for - separating concerns. The idea is that you do what you want to do on the Model and leave the task of updating the View to the framework.

And it works well too, if only you remember not to use the naive implementation for anything but the simplest models.

Reply Parent Score: 2