Dear list and conference members,
Thanks for your comments/suggestions in regards to the Messaging Design Pattern (17th conference on Pattern Languages of Programs - PLoP 2010). I plan to address them shortly. Let me start by saying that the first paper is not comprehensive in terms of the MDP work. Several MDP aspects are mentioned in general terms. There is another related paper (Messaging Design Pattern and a Distributed Component/Service Model). Please find enclosed a link to it: https://jt.dev.java.net/files/documents/5553/149793/MDPdistributedModel.pdf This paper may help clarify/answer some of your comments/suggestions. For instance, it presents a concrete problem area that MDP is able to solve. It also demonstrates how MDP is used for the implementation of distributed systems. By the way, the references include a link to a Java Design Pattern Framework (version 7.0). This public framework, based on MDP, has been utilized for the implementation of production quality applications (including distributed applications). I would appreciate any additional comments/suggestions that you may have. This second paper will be submitted for publication in the near future. Regards Messaging Design Pattern and a Distributed Component/Service Model This paper discusses a distributed component model based on the messaging design pattern (MDP). This pattern is utilized to implement transparent and secure access to remote components in a distributed environment.Interchange of information (i.e. messaging) is an inherent part of the world around us. Messaging is a ubiquitous. Conventional software methodologies and distributed component technologies/models overlook messaging and therefore provide an incomplete model. Implementation of distributed applications becomes a complex undertaking. On the other hand, a messaging paradigm and the associated messaging design pattern address this gap and provide a more complete and accurate model of the real world. As a consequence, software engineering processes and techniques are improved significantly. While designing and manufacturing distributed software, we need to think not only in terms of software components but also in terms of the messaging being exchanged between components. Moreover these two aspects need to be viewed and addressed as being independent of each other (decoupled). Both are key aspects. Several distributed technologies have been proposed and built. Traditional technologies and models not based on MDP present a variety of shortcomings and problems: a) Lack of interoperability. b) Complexity and rigidity. c) Language, platform, protocol and data format dependencies. d) Proprietary. These problems negatively impact software engineering processes in terms of cost, timeframe, overall quality, etc. Service Oriented Architecture (SOA) Technologies address some of these issues. On the hand, some of the shortcomings and complexities still remain because these solutions are not based on a messaging (MDP) paradigm. Most of these technologies are still based on remote procedure/method invocation. MDP has also been used for the implementation of SOA and Enterprise Service Bus (ESB) technologies. At the core of these technologies lies the need for communication between components and applications. This communication challenge is exactly the one that MDP targets, models and solves. --- On Wed, 10/6/10, Messaging Design Pattern <[email protected]> wrote: From: Messaging Design Pattern <[email protected]> Subject: PLoP2010 Paper - Messaging Design Pattern and Pattern Implementation To: [email protected], "gang_of_4_list" <[email protected]>, "TelePLoP List" <[email protected]>, [email protected] Date: Wednesday, October 6, 2010, 6:55 PM Dear List Members, I'm pleased to inform you that the following paper was accepted for publication in the 17th conference on Pattern Languages of Programs - PLoP 2010. Your earlier feedback is appreciated. Special thanks and kind words of acknowledgment to Dr.Hironori Washizaki for all his suggestions and recommendations for improvement. Best regards, Messaging Design Pattern and Pattern Implementationhttps://jt.dev.java.net/files/documents/5553/150311/designPatterns.pdf Abstract Interchange of information (i.e. messaging) is an inherent part of nature and man-made processes. Messaging is a ubiquitous part of the world around us. Conventional software methodologies and component technologies overlook messaging and therefore provide an incomplete model. On the other hand, a messaging paradigm and the associated messaging design pattern (MDP) address this gap and provide a more complete and accurate model of the real world. As a consequence, software engineering processes and techniques are improved significantly. While designing and manufacturing software, we need to think not only in terms of software components, but also in terms of the messaging being exchanged between these entities. Encapsulation, decoupling and reusability are improved while reducing complexity. This paper also discusses how the messaging design pattern is utilized to implement or help implement other well-known design patterns like Gang of Four design patterns (GoF), Data Access Objects (DAOs), and J2EE design patterns. Keep in mind that most of the design patterns are, at some level, responsible for interchanging information between participants. The overall design and UML diagrams are simplified and streamlined making them easier to understand and implement. The resulting software design and implementation are also more robust and straightforward. Design patterns implemented using MDP, can be reused to provide transparent and secure access to remote components/services as the basis for a complete distributed component model.
_______________________________________________ telecom-patterns mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/telecom-patterns
