We all know what high- and low-level means to programming languages. This post tries to apply the concept to concurrent programming models/techniques.
FM Lite is a specially tailored subset of FM that aims to complete with threads and multithreading.
Fast Messenger provides FutureReply a mechanism similar to the Future in Java. Sequential OO programs may keep the same program flow while enjoying high concurrency out of asynchronous messaging. When you obtain an instance of FutureReply by sending out a message, your code will continue without blocking. You can perform any work before you decide to check whether a reply is ready. Even the checking offers you two options, you can check, leave (non-blocking) and come back later, or you can wait (blocking) until a reply is ready.
This post revisits the active object implementation of the quick sort example, and introduces basic concepts of active object model provided by Fast Messenger. In the post I will explain what active objects are, how they identify themselves, how they address each other, and how they communicate with codes found in the quick sort example. (This post will not cover features not found in the example.)
This post describes two concurrent implementations of quick sort algorithm. One version uses active objects (provided by Fast Messenger) for concurrence, while the other version uses traditional multithreading.
The post describes three implementations of the Fibonacci function. Each implementation demonstrates a different programming model: sequential, multi-thread and active-object programming.