Linked by Hadrien Grasland on Fri 27th May 2011 11:34 UTC
Thread beginning with comment 474945
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
AS MQSeries originated on the IBM Mainframe then I'd say we are in agreement.
As for 1975/76. I was using a DEC PDP-11.
Both the RSX-11 & the RT-11 Operating systems were Async IO based. Writing device drivers for them and also VMS was a really enjoyable experience.
The concept of an AST (Asynchronous System Trap) is really nice. This is a bit of code that gets executed when the I/O you have requested completes.




Member since:
2011-01-28
shotsman,
"There have been Operating Systems that implement Asynchronous I/O in existance for years."
All the posts saying this is "old news" are completely missing the point - nobody's claiming that it is "new". If articles were restricted to "news", then we'd be left with legal articles and product announcements with very little technical merit at all.
All of us know that many models have been exploited in computing history. It's still a good question to ask which model best fits today, and the fact that there is a debate on these topics is a good thing in my opinion.
That said, thank you for your recollections!
"I first programmed one in 1975/6. It was called RSX11-D"
Was this a parallel computer?
"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."
IBM mainframe computers use this mechanism almost exclusively. biztalk does it too. I think it's a powerful and scalable concept which is lost in modern CS courses.