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 474812
To read all comments associated with this story, please click here.
by essen on Fri 27th May 2011 13:29 UTC
Member since:

We've been doing this in Erlang for years. All processes are entirely separate and communicate asynchronously. Synchronized communication can also be achieved by waiting for a response and monitoring the process. All this is already available in the standard library and you just have to write functions like you would in a sequential language, despite everything executing in parallel.

Reply Score: 2

RE: Erlang
by shmerl on Sun 29th May 2011 01:46 in reply to "Erlang"
shmerl Member since:

+1 for Erlang!

Reply Parent Score: 2

RE[2]: Erlang
by Kochise on Mon 30th May 2011 01:26 in reply to "RE: Erlang"
Kochise Member since:

+11 for Erlang!


Reply Parent Score: 2