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 474909
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Callback fragmentation
by Neolander on Sun 29th May 2011 07:38 UTC in reply to "RE[2]: Callback fragmentation"
Member since:

Point taken ;)

(Partly because of your explanation, and partly because I've also thought that preventing a notification to be fired at fast rates prevents local DoS attacks on things which don't need extreme reactivity)

Reply Parent Score: 1