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 474825
To read all comments associated with this story, please click here.
Multithreading versus event handling
by Abacus_ on Fri 27th May 2011 15:14 UTC
Abacus_
Member since:
2006-12-08

Actually this is a very old topic. John Ousterhout gave an excellent talk about multithreading versus event handling in 1996: John Ousterhout, Why Threads Are A Bad Idea (for most purposes), Invited talk of the USENIX Winter Technical Conference, Jan, 1996, http://www.csd.uoc.gr/~hy527/papers/threads-ousterhout.pdf.

Another interesting paper is this one: Rob von Behren, Jeremy Condit, Eric Brewer, Why Events Are a Bad Idea
(for High-Concurrency Servers) (2003), 9th Workshop on Hot Topics in Operating Systems (HotOS IX), 2003,
http://capriccio.cs.berkeley.edu/pubs/threads-hotos-2003.pdf.

Reply Score: 2