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 474887
To read all comments associated with this story, please click here.
RE: Callback fragmentation
by Neolander on Sat 28th May 2011 09:48 UTC in reply to "Callback fragmentation"
Neolander
Member since:
2010-03-08

I don't understand: why would the code require a notification each time a data structure changes after having started a big operation on it, instead of asking for a notification once the big operation is over? More important, why would they put a very intensive callback function on something as fine-grained as changing a data structure ?

If you can prove that this is a valid use case and not poor programming practices at work, a feature that gives notifications a "cooldown time" could indeed be the right answer.

Edited 2011-05-28 09:52 UTC

Reply Parent Score: 1