Practicing the Chain of Responsibility Pattern
page 8 of 8
by Xianzhong Zhu
Feedback
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 33835/ 74

Summary

In this article, we have succeeded in building up a remote service manager application. By introducing the Chain of Responsibility design pattern and reasonably applying the Template Method pattern, we have not only removed the switch branch sentence in the original design, but guaranteed code reusing as much as possible. Although, in this simple service manager application, we have not provided more extension points to enhance the system for the future and the introduction of the both patterns above have not shown apparent privileges, the whole design seems elegant and filled with the beauty of design.

On the other hand, purely for the sake of showing off the beauty of design and increasing the complexity of design seems "concentrating on too many details with excessive design." But, put in the larger application environment, the design of the latter doubtless has more general use.

Therefore, to weigh whether a design is an "excessive design" or not needs to be evaluated and analyzed deliberatively and from several angles. In the practical scenarios, with the help of the design patterns we are probable to establish better designs. However, whether it is indeed necessary to introduce the related design patterns depends upon the facts in the end.


View Entire Article

User Comments

No comments posted yet.

Product Spotlight
Product Spotlight 





Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2021 ASPAlliance.com  |  Page Processed at 2021-11-29 1:01:36 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search