This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Because of the limits imposed on developing faster computers, the only way forwards is going to be multi-processor computer. To take advantage of those systems we need to design our application to take advantage of this different architecture. Concurrent design is the future much the same way that Object Oriented technology has today.
I want to know if the Command Pattern makes concurrent design simpler to implement. I don�t understand the implication of using Command Pattern in a concurrent application.
Command is nicely suited to parallel processing. If I want to ask another thread (potentially on another processor or JVM) to do a task I encapsulate the task in a Command and pass it along. I can pass new commands to another process without warning because it will execute anything with the proper interface.
For cluster management I execute Commands and gather information from six servers in a cluster by passing the command name, not the command itself. That's not quite as kool becuase I have to deploy the commands to the servers.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com