3.8 Conclusion

---

3.8 Conclusion

Concurrent programs can often be effectively implemented using active and passive objects. This is true of many types of concurrent programs, including distributed programs. In these models, the most interesting part will be the passive object, which is a component. It is the most interesting because it is used to implement the coordination that allows the concurrent program to do useful work. One very powerful way to implement passive objects is through the use of state diagrams. State diagrams allow a programmer to reason about the behavior of the passive object. These state diagrams can then easily be translated into working Java programs. The reader should note that state diagrams are easily translated into Java objects because of the language constructs, such as synchronization, wait, and notify, so the design of these objects makes sense in languages that support the design of monitors, such as Java and Ada, but are difficult to implement in languages such as C/C++ that do not.

---