notification system design patterns

Content1. Introduction to Design Patterns2. Design Pattern classification3. Design mode 6 principles1. Introduction to Design PatternsDesign mode (Patterns)--the basis of reusable object-oriented softwareDesign patterns are a set

behavior that may change and make it open. It contains three meanings: first, the interface and abstract class are used to limit the boundaries of the extension. Public methods that do not exist in the interface or abstract class are not allowed; second, the parameter type and referenced object should try to use interfaces or abstract classes instead of implementation classes. Third, the abstraction layer remains stable and cannot be modified once determined. 2) metadata (metadata) controls

Why design patterns? Let's take a look at the six principles and use the design pattern principles. Introduction　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　 I don't like reading books very much, because I forgot to read ten lines of books, so I read the left teacher and copied it to improve my memory. This is the http://www.cnblogs.com/zuoxiaolong/p/pattern1.html of o

Design patterns give me a lot of benefits, there are more than 20 kinds of design patterns in Java, and there are five common design patterns in PHP, let's take a closer look at the factory pattern in PHP

version), do you think this is still a basic Java language book? But it is not purely because the author of this book cleverly integrates the object-oriented thinking into the specific Java technology, it makes you feel the birth of a new language and a new way of thinking. However, after reading this book, you may need a clearer, more systematic, and more thorough understanding of these ideas in the book, so you need to study gof's design

that may occur when improving the program structure in combination with the design pattern: excessive attention to the flexibility of the program structure. In this way, it is easy to reconstruct the program structure from the perspective of whether it can bring flexibility to the design. In the end, the system may be complicated, chaotic, hard to understand, an

version), do you think this is still a basic Java language book? But it is not purely because the author of this book cleverly integrates the object-oriented thinking into the specific Java technology, it makes you feel the birth of a new language and a new way of thinking. However, after reading this book, you may need a clearer, more systematic, and more thorough understanding of these ideas in the book, so you need to study gof's design

objects; The new object is used to re-use its existing functions by delegating methods that call existing objects. In short: Use the combination/aggregation relationship as much as possible, with less inheritance.7, Dimitri Law (least known principle) (Demeter Principle)Why is it called the least known principle, that is to say: an entity should be as small as possible interaction with other entities, so that the system function module is relatively

and concretecreator (because here I use anoperation to encapsulate the two methods in product, so I didn't even see the shadow of the product. Of course, it is good to put the specific call of the method in the product into the customer program ). Package COM. andyidea. patterns. client; import COM. andyidea. patterns. concretecreator. circlefactory; import COM. andyidea.

design mode A book introduces design patterns to the software community, which is written by Erich Gamma, Richard Helm, Ralph Johnson, and John vlissides design (commonly known as "Gang of Four"). The core concepts behind the design patt