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 474898
To read all comments associated with this story, please click here.
Old News
by shotsman on Sat 28th May 2011 17:30 UTC
Member since:

There have been Operating Systems that implement Asynchronous I/O in existance for years.
I first programmed one in 1975/6. It was called RSX11-D

The basic IO call was QIO ( Queue !!!!! I/O )
OOTB it was Asynchronous.
If you wanted is Synchronous you used the QIOW version
(Queue I/O & Wait)

You would issue a QIO call and sometime later either test an event flag or an AST (Asynchtonous System Trap) would be fired.

This was carried over into VMS and is still there today.

There are many Async queueing/messaging products around. However many people (more used to WebServices & Unix) find it difficult to accept 'Fire & Forget' operations. I use one of these every day. It is called WebSphere MQ or good old MQSeries. You can turn it into a Request/Reply model if you want but with reliable delivery why not drop a message onto a queue and then get on with doing something else.
I studied Queueing Theory as an undergad in 1975 and wrote a Software Queueing system in 1981 at DEC. IT was Async in operation. IT was embedded in another product.
For me doing things synchronously is ... well just wrong. We live in an async world. Why is so much software written using the Synchronous model? Laziness I suppose.

Reply Score: 4