DOCSLIB.ORG

Design Patterns the Gang of Four Suggests a Few Strategies Outline for Lecture 22 for Creating Good O-O Designs, Including … I

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Design Patterns the Gang of Four Suggests a Few Strategies Outline for Lecture 22 for Creating Good O-O Designs, Including … I Design Patterns The Gang of Four suggests a few strategies Outline for Lecture 22 for creating good o-o designs, including … I. Specific design • Design to interfaces. patterns A. Façade • Favor composition over inheritance B. Adapter • Find what varies and encapsulate C. Singleton it D. Iterator E. Factories Façade One of the simplest patterns is Façade. Its purpose is to … “provide a unified interface to a set of interfaces in a subsystem. Façade defines a higher-level interface that makes the subsystem easier to use.” [GoF, p. 185] In other words, the purpose of façade is to provide an interface that is simpler to use. We’ve seen an example of this in one of the last two or three lectures. What is it? Façade Subsystem classes Lecture 22 Object-Oriented Languages and Systems 1 Façade Intent: You want to use an existing system. You need to define your own interface. Problem: You need to use only a subset of a complex system. Solution: Present a new interface to the client of the existing system. Implementation: Define a new class that has the required interface, and have it use the existing system. Can you think of another example of Façade? Adapter The Adapter pattern is similar to Façade. However, in this case, we have an existing interface that we are trying to design to. Consider the case where we need to store an ordered collection of String s. We want to do certain things with these String s: • get the ith string • insert a String in the ith position • return the number of String s in the collection • remove and return the ith String • remove and discard all String s Now, one way to implement this is to create a LinkedList of String s ( LinkedList<String> ). What’s wrong with that? (What does Skrien say? What is still wrong with it?) Remember the GoF’s first strategy for creating good o-o design? Let’s specify what we want our StringList to do: CSC/ECE 517 Lecture Notes © 2007, Edward F. Gehringer 2 public interface StringList { //get the i-th string public String get(index i); //remove and return the i-th string public String remove(index i); //insert s in the i-th position public void insertElementAt(String s, index i); //remove and discard all strings public void clear(); //return the # of strings in the collection public int size(); } Where do we find a class to implement the StringList interface? There’s no Java class with exactly this behavior, although LinkedList and ArrayList are close. An elegant solution is to introduce an adapter class, which delegates all of the functionality to a hidden class such as LinkedList . Here is an implementation using the old, non-generic, LinkedList : Lecture 22 Object-Oriented Languages and Systems 3 public class StringListAdapter implements StringList { private LinkedList v = new LinkedList(); //get the i-th string public String get(index i) { return (String) v.get(i); } //remove and return the i-th string public String remove(index i) { return (String) v.remove(i); } //insert s in the i-th position public void insertElementAt(String s, index i) { v.insertElementAt(s, i); } //remove and discard all strings public void clear() { v.clear(); } //return the number of strings in the list public int size() { return v.size(); } } If we had had such a class in our program under Java 1.4, we could easily have changed it to use the generic LinkedList in Java 1.5. Adapter Intent: Match an existing object to a particular interface. Problem: A system has the right data and behavior but the wrong interface. Typically used when you have to make something a derivative of an abstract class you already have or are defining. Solution: The adapter provides a “wrapper” with the desired interface. CSC/ECE 517 Lecture Notes © 2007, Edward F. Gehringer 4 Implementation: Contain the existing class in another class. Have the containing class match the required interface and call the methods of the contained class. Adapter and Façade have many similarities. They are both wrappers, but they are different kinds of wrappers. Let’s compare them. Façade Adapter Are there preexisting classes? Is there an interface we must design to? Does an object need to behave polymorphically? Is a simpler interface needed? Can you think of another example of Adapter? Singleton The Singleton pattern is used to ensure that only one object of a particular class is instantiated. It can be implemented by having either— • an instance variable that “contains” (references) the desired object, or • a special method that instantiates the desired object. To make sure that objects are not created in any other way (viz., by using the constructor), define the constructor of the class to be protected or private. For example, suppose we are writing a program that plays bridge. • When we deal the cards, we start with a card deck that contains 52 cards. • We don’t want to create the deck every time we deal, so we simply create the card deck once at the start of the program and copy it whenever we need it. Lecture 22 Object-Oriented Languages and Systems 5 Our initial card deck is a singleton. There are at least three ways to implement a Singleton in Java: 1. Use an instance variable to create the object when the class is loaded: public class Singleton { public static final Singleton instance = new Singleton(); private Singleton() { } //...any other methods... } 2. Create the instance when the class is loaded, but provide a method to get the instance variable. public class Singleton { private static final Singleton instance = new Singleton(); private Singleton() { } public static Singleton getInstance() { return instance; } ...any other methods... } Note that the singleton is used differently than in the first case: Case 1: Singleton s = Singleton.instance; Case 2: Singleton s = Singleton.getInstance(); 3. Use lazy initialization to create the instance. • When the getInstance() method is called, it checks to see if the object has already been instantiated. If it has, the method simply returns (a reference to) the object. CSC/ECE 517 Lecture Notes © 2007, Edward F. Gehringer 6 If it hasn’t, the method instantiates it and returns a reference to the object. What is the advantage of doing this? Singleton Intent: Prevent the instantiation of multiple objects of this class. Problem: Several different client objects need to refer to the same thing, and you want to ensure that you do not have more than one of them. Solution: Guarantees one instance. Implementation: Use a private or protected constructor, and provide a public instance variable or method that creates the object exactly once. Iterator Remember Smalltalk’s do: method? It would iterate over any kind of Collection . Why is this a useful method to have? Let’s see how the same effect can be achieved in Java. Since Java 1.1, Java has allowed classes to be nested within other classes. A class defined inside another class is known as an inner class . Inner classes are useful for at least two reasons: • The name of the inner class is known only within its scope. Thus, it does not “pollute” the namespace of the package. • The code of an inner class can refer directly to names from enclosing scopes, including both class and instance varia- bles and methods, and local variables of enclosing blocks. A Fixed Stack Lecture 22 Object-Oriented Languages and Systems 7 Here is an example adapted from the Java tutorial documentation, a class FixedStack , which implements a stack, and defines an iterator of elements from the stack, from top to base: public class FixedStack { Object array[]; int top = 0; FixedStack(int fixedSizeLimit) { array = new Object[fixedSizeLimit]; } public void push(Object item) { array[top++] = item; } public boolean isEmpty() { return top == 0; } // other stack methods go here... /** This adapter class is defined as part of its * target class, It is placed alongside the * variables it needs to access. */ class Iterator implements java.util.Iterator { int count = top; public boolean hasNext() { return count > 0; } public Object next() { if (count == 0) throw new java.util.NoSuchElementException ("FixedStack"); return array[--count]; } public void remove() { … } } public java.util.Iterator elements() { return new Iterator(); } } The interface java.util.Iterator is used to communicate a series of values to a client. CSC/ECE 517 Lecture Notes © 2007, Edward F. Gehringer 8 Note that FixedStack does not directly implement the Iterator interface. Why not? Thus, a separate adapter class is used to return the elements one by one. Note that the adapter class needs to access the array containing the stack elements. It can directly refer to instance variables of the stack, since the adapter is defined inside FixedStack . Iterator Intent: Allow clients to iterate over the elements of a collection without knowing how the collection is implemented. Problem: Collections may be implemented in many ways, with different ways of moving from one item to the next. If the implementation of the collection changes, the code for sequencing over it may have to change too. Solution: Provide a standard interface for starting an iteration, moving to the next element, and determining whether the end of the collection has been reached. Implementation: Implement each of the above methods for each type of collection; then callers can simply call them to iterate over the collection. Factories Suppose we have a class X that needs to iterate over some FixedStack s. For example, it may want to take the cross-product of the elements in two FixedStack s to produce a matrix. In order to do this, X should not create the iterator itself. Why not? Instead, it should call which method? Lecture 22 Object-Oriented Languages and Systems 9 Class FixedStack is serving as a “factory” of iterators.
Load more

Recommended publications
  • Design Patterns in PHP and Laravel — Kelt Dockins Design Patterns in PHP and Laravel
    Design Patterns in PHP and Laravel — Kelt Dockins Design Patterns in PHP and Laravel Kelt Dockins [email protected] Design Patterns in PHP and Laravel Kelt Dockins Dolph, Arkansas USA ISBN-13 (pbk): 978-1-4842-2450-2 ISBN-13 (electronic): 978-1-4842-2451-9 DOI 10.1007/978-1-4842-2451-9 Library of Congress Control Number: 2016961807 Copyright © 2017 by Kelt Dockins This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made.
    [Show full text]
  • Process Synchronisation Background (1)
    Process Synchronisation Background (1) Concurrent access to shared data may result in data inconsistency Maintaining data consistency requires mechanisms to ensure the orderly execution of cooperating processes Producer Consumer Background (2) Race condition count++ could be implemented as register1 = count register1 = register1 + 1 count = register1 count- - could be implemented as register2 = count register2 = register2 - 1 count = register2 Consider this execution interleaving with ―count = 5‖ initially: S0: producer execute register1 = count {register1 = 5} S1: producer execute register1 = register1 + 1 {register1 = 6} S2: consumer execute register2 = count {register2 = 5} S3: consumer execute register2 = register2 - 1 {register2 = 4} S4: producer execute count = register1 {count = 6 } S5: consumer execute count = register2 {count = 4} Solution: ensure that only one process at a time can manipulate variable count Avoid interference between changes Critical Section Problem Critical section: a segment of code in which a process may be changing Process structure common variables ◦ Only one process is allowed to be executing in its critical section at any moment in time Critical section problem: design a protocol for process cooperation Requirements for a solution ◦ Mutual exclusion ◦ Progress ◦ Bounded waiting No assumption can be made about the relative speed of processes Handling critical sections in OS ◦ Pre-emptive kernels (real-time programming, more responsive) Linux from 2.6, Solaris, IRIX ◦ Non-pre-emptive kernels (free from race conditions) Windows XP, Windows 2000, traditional UNIX kernel, Linux prior 2.6 Peterson’s Solution Two process solution Process Pi ◦ Mutual exclusion is preserved? ◦ The progress requirements is satisfied? ◦ The bounded-waiting requirement is met? Assumption: LOAD and STORE instructions are atomic, i.e.
    [Show full text]
  • Dependency Injection in Unity3d
    Dependency Injection in Unity3D Niko Parviainen Bachelor’s thesis March 2017 Technology, communication and transport Degree Programme in Software Engineering Description Author(s) Type of publication Date Parviainen, Niko Bachelor’s thesis March 2017 Language of publication: English Number of pages Permission for web publi- 57 cation: x Title of publication Dependency Injection in Unity3D Degree programme Degree Programme in Software Engineering Supervisor(s) Rantala, Ari Hämäläinen, Raija Assigned by Psyon Games Oy Abstract The objective was to find out how software design patterns and principles are applied to game development to achieve modular design. The tasks of the research were to identify the dependency management problem of a modular design, find out what the solutions offered by Unity3D are, find out what the dependency injection pattern is and how it is used in Unity3D environment. Dependency management in Unity3D and the dependency injection pattern were studied. Problems created by Unity3D’s solutions were introduced with examples. Dependency in- jection pattern was introduced with examples and demonstrated by implementing an ex- ample game using one of the available third-party frameworks. The aim of the example game was to clarify if the use of dependency injection brings modularity in Unity3D envi- ronment and what the cost of using it is. The principles of SOLID were introduced with generic examples and used to assist depend- ency injection to further increase the modularity by bringing the focus on class design. Dependency injection with the help of SOLID principles increased the modularity by loosely coupling classes even though slightly increasing the overall complexity of the architecture.
    [Show full text]
  • Singleton Pattern: Motivation • Sometimes Need an Object That Is Unique – There Will Only Be a Single Instance of the Class
    Singleton Pattern: Motivation • Sometimes need an object that is unique { There will only be a single instance of the class • Could be done with a global variable, BUT { Such an instance would exist for the duration of the program { If the instance were resource-intensive, this could be a problem { It would be better to create such an object only on an as-needed basis 1 Singleton Pattern: Defined • Singleton Pattern (177): Ensures a class has only one instance, and provides a global point of access to it. • The class manages a single instance of itself. • No other classes can create an instance of a singleton on their own. { I.e., another class cannot execute newInstance = new SingletonClass() • The singleton provides the means for other classes to access the instance. • Class diagram: • The question is: How to implement this so that we can insure that no more than one instance can be created? 2 Singleton Pattern: Implementation • We know that if we have a public constructor for a class, instances can be created by any other classes • But if we make the constructor private, only objects of the class could call the constructor, but then how could a first object of the class be created? { I.e., The only way to create an object of the class is to already have an object of the class (chicken and egg problem) • The trick is to have a private constructor but a static method that creates instances of the class { Since we're dealing with a singleton, the static method will include code that insures that only a single instance of the class will be created • Sample code: public class Singleton { private static Singleton uniqueInstance; private Singleton() { } public static Singleton getInstance() { if (uniqueInstance == null) uniqueInstance = new Singleton(); return uniqueInstance; } ..
    [Show full text]
  • Designpatternsphp Documentation Release 1.0
    DesignPatternsPHP Documentation Release 1.0 Dominik Liebler and contributors Jul 18, 2021 Contents 1 Patterns 3 1.1 Creational................................................3 1.1.1 Abstract Factory........................................3 1.1.2 Builder.............................................8 1.1.3 Factory Method......................................... 13 1.1.4 Pool............................................... 18 1.1.5 Prototype............................................ 21 1.1.6 Simple Factory......................................... 24 1.1.7 Singleton............................................ 26 1.1.8 Static Factory.......................................... 28 1.2 Structural................................................. 30 1.2.1 Adapter / Wrapper....................................... 31 1.2.2 Bridge.............................................. 35 1.2.3 Composite............................................ 39 1.2.4 Data Mapper.......................................... 42 1.2.5 Decorator............................................ 46 1.2.6 Dependency Injection...................................... 50 1.2.7 Facade.............................................. 53 1.2.8 Fluent Interface......................................... 56 1.2.9 Flyweight............................................ 59 1.2.10 Proxy.............................................. 62 1.2.11 Registry............................................. 66 1.3 Behavioral................................................ 69 1.3.1 Chain Of Responsibilities...................................
    [Show full text]
  • Lecture 26: Creational Patterns
    Creational Patterns CSCI 4448/5448: Object-Oriented Analysis & Design Lecture 26 — 11/29/2012 © Kenneth M. Anderson, 2012 1 Goals of the Lecture • Cover material from Chapters 20-22 of the Textbook • Lessons from Design Patterns: Factories • Singleton Pattern • Object Pool Pattern • Also discuss • Builder Pattern • Lazy Instantiation © Kenneth M. Anderson, 2012 2 Pattern Classification • The Gang of Four classified patterns in three ways • The behavioral patterns are used to manage variation in behaviors (think Strategy pattern) • The structural patterns are useful to integrate existing code into new object-oriented designs (think Bridge) • The creational patterns are used to create objects • Abstract Factory, Builder, Factory Method, Prototype & Singleton © Kenneth M. Anderson, 2012 3 Factories & Their Role in OO Design • It is important to manage the creation of objects • Code that mixes object creation with the use of objects can become quickly non-cohesive • A system may have to deal with a variety of different contexts • with each context requiring a different set of objects • In design patterns, the context determines which concrete implementations need to be present © Kenneth M. Anderson, 2012 4 Factories & Their Role in OO Design • The code to determine the current context, and thus which objects to instantiate, can become complex • with many different conditional statements • If you mix this type of code with the use of the instantiated objects, your code becomes cluttered • often the use scenarios can happen in a few lines of code • if combined with creational code, the operational code gets buried behind the creational code © Kenneth M. Anderson, 2012 5 Factories provide Cohesion • The use of factories can address these issues • The conditional code can be hidden within them • pass in the parameters associated with the current context • and get back the objects you need for the situation • Then use those objects to get your work done • Factories concern themselves just with creation, letting your code focus on other things © Kenneth M.
    [Show full text]
  • Is 18 Factoriessingleton.Pdf
    Vincenzo Gervasi, Laura Semini Ingegneria del Software Dipartimento di Informatica Università di Pisa “Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice” ▪ -- Christopher Alexander A Pattern Language, 1977 C. Alexander ha definito i design patterns studiando tecniche per migliorare il processo di progettazione di edifici e aree urbane Ogni pattern è una regola in tre parti, che esprime una relazione tra ▪ Un contesto ▪ Un problema ▪ Una soluzione DEF: “una soluzione a un problema in un contesto” I pattern possono essere applicati a diverse aree, compreso lo sviluppo software analysis design Architetural implementation Detailed • coding maintenance • unit testing • integration • system testing Sono 23 design pattern suddivisi in base al loro scopo Creazionali: ▪ propongono soluzioni per creare oggetti Comportamentali: ▪ propongono soluzioni per gestire il modo in cui vengono suddivise le responsabilità delle classi e degli oggetti Strutturali: ▪ propongono soluzioni per la composizione strutturale di classi e oggetti Factory: a class whose sole job is to easily create and return instances of other classes Creational patterns abstract the object instantiation process. ▪ They hide how objects are created and help make the overall system independent of how its objects are created and composed. ▪ They make it easier to construct
    [Show full text]
  • C++ and the Perils of Double-Checked Locking ∗
    C++ and the Perils of Double-Checked Locking ∗ Scott Meyers and Andrei Alexandrescu September 2004 Multithreading is just one damn thing after, before, or simultaneous with another. 1 Introduction Google the newsgroups or the web for the names of various design patterns, and you’re sure to find that one of the most commonly mentioned is Singleton. Try to put Singleton into practice, however, and you’re all but certain to bump into a significant limitation: as traditionally implemented (and as we explain below), Singleton isn’t thread-safe. Much effort has been put into addressing this shortcoming. One of the most popular approaches is a design pattern in its own right, the Double-Checked Locking Pattern (DCLP) [13, 14]. DCLP is designed to add efficient thread- safety to initialization of a shared resource (such as a Singleton), but it has a problem: it’s not reliable. Furthermore, there’s virtually no portable way to make it reliable in C++ (or in C) without substantively modifying the conven- tional pattern implementation. To make matters even more interesting, DCLP can fail for different reasons on uniprocessor and multiprocessor architectures. This article explains why Singleton isn’t thread safe, how DCLP attempts to address that problem, why DCLP may fail on both uni- and multiprocessor ar- chitectures, and why you can’t (portably) do anything about it. Along the way, it clarifies the relationships among statement ordering in source code, sequence points, compiler and hardware optimizations, and the actual order of statement execution. Finally, it concludes with some suggestions regarding how to add thread-safety to Singleton (and similar constructs) such that the resulting code is both reliable and efficient.
    [Show full text]
  • Creational Patterns
    9. Creational Pattern Venkat Subramaniam CDP-1 Creational Patterns • Abstracts instantiation process • Makes system independent of how its objects are œ created œ composed œ represented • Encapsulates knowledge about which concrete classes the system uses • Hides how instances of these classes are created and put together Venkat Subramaniam CDP-2 Abstract Factory Provide an interface for creating families of related or dependent objects without specifying their concrete classes Venkat Subramaniam CDP-3 Example that would benefit from Abstract Factory ComputerModelA MemoryType A CPUTypeA ModemTypeA BuildComputer(ComputerModelA& comp) { comp.Add(new MemoryTypeA); comp.Add(new CPUTypeA); comp.Add(new ModemTypeA); } What if I want to build a Computer of Model B with Model B Memory,CPU and Modem? Venkat Subramaniam CDP-4 Using Abstract Factory ComputerFactory Client Computer createComputer() createMemory() createCPU() Computer Computer createModem() ModelA ModelB Memory CompFactoryB CompFactoryA createComputer() createComputer() Memory Memory createMemory() createMemory() ModelA ModelB createCPU() createCPU() createModem() createModem() Venkat Subramaniam CDP-5 Using Abstract Factory... BuildComputer(Computer& comp, ComputerFactory& compFactory) { comp.Add(compFactory.createMemory()) ; comp.Add(compFactory.createCPU()); comp.Add(compFactory.createModem()); } Venkat Subramaniam CDP-6 .hen to use Abstract Factory? • Use Abstract Factory when: œ system should be independent of how its products are created, composed and represented œ system should
    [Show full text]
  • Abstract Factory and Singleton Design Patterns to Create Decorator Pattern Objects in Web Application
    International Journal of Advanced Information Technology (IJAIT) Vol. 1, No.5, October 2011 ABSTRACT FACTORY AND SINGLETON DESIGN PATTERNS TO CREATE DECORATOR PATTERN OBJECTS IN WEB APPLICATION Vijay K Kerji Department of Computer Science and Engineering, PDA College of Engineering,Gulbarga, India [email protected] ABSTRACT Software Design Patterns are reusable designs providing common solutions to the similar kind of problems in software development. Creational patterns are that category of design patterns which aid in how objects are created, composed and represented. They abstract the creation of objects from clients thus making the application more adaptable to future requirements changes. In this work, it has been proposed and implemented the creation of objects involved in Decorator Design Pattern. (Decorator Pattern Adds Additional responsibilities to the individual objects dynamically and transparently without affecting other objects). This enhanced the reusability of the application design, made application more adaptable to future requirement changes and eased the system maintenance. Proposed DMS (Development Management System) web application is implemented using .NET framework, ASP.NET and C#. KEYWORDS Design Patterns, Abstract Factory, Singleton, Decorator, Reusability, Web Application 1. INTRODUCTION Design Patterns refer to reusable or repeatable solutions that aim to solve similar design problems during development process. Various design patterns are available to support development process. Each pattern provides the main solution for particular problem. From developer’s perspectives, design patterns produce a more maintainable design. While from user’s perspectives, the solutions provided by design patterns will enhance the usability of web applications [1] [2]. Normally, developers use their own design for a given software requirement, which may be new each time they design for a similar requirement.
    [Show full text]
  • Java Design Patterns I
    Java Design Patterns i Java Design Patterns Java Design Patterns ii Contents 1 Introduction to Design Patterns 1 1.1 Introduction......................................................1 1.2 What are Design Patterns...............................................1 1.3 Why use them.....................................................2 1.4 How to select and use one...............................................2 1.5 Categorization of patterns...............................................3 1.5.1 Creational patterns..............................................3 1.5.2 Structural patterns..............................................3 1.5.3 Behavior patterns...............................................3 2 Adapter Design Pattern 5 2.1 Adapter Pattern....................................................5 2.2 An Adapter to rescue.................................................6 2.3 Solution to the problem................................................7 2.4 Class Adapter..................................................... 11 2.5 When to use Adapter Pattern............................................. 12 2.6 Download the Source Code.............................................. 12 3 Facade Design Pattern 13 3.1 Introduction...................................................... 13 3.2 What is the Facade Pattern.............................................. 13 3.3 Solution to the problem................................................ 14 3.4 Use of the Facade Pattern............................................... 16 3.5 Download the Source Code.............................................
    [Show full text]
  • Table of Contents
    Table of Contents ± -—T^jTp^om Object-Oriented to Functional Programming 5 Chajava- an introduction 5 java programming paradigms 6 CO imperative programming CD Real-life imperative example Object-oriented paradigm 7 Objects and classes 7 Encapsulation 7 Abstraction 8 Inheritance 8 Polymorphism 9 Declarative programming 10 Functional programming 11 Working with collections versus working with streams 11 An introduction to Unified Modeling Language 12 Class relations 14 Generalization 15 Realization 15 Dependency 16 Association 16 Aggregation 16 Composition 17 Design patterns and principles 17 Single responsibility principle 18 Open/closed principle 20 Liskov Substitution Principle 20 Interface Segregation Principle 22 Dependency inversion principle 23 Summary 24 Chapter 2: Creational Patterns 27 Singleton pattern 27 Synchronized singletons 29 Synchronized singleton with double-checked locking mechanism 30 Lock-free thread-safe singleton 30 tu * y and lazy loacling 31 i he factory pattern 31 Simple factory pattern 32 Table of Contents Static factory 33 Simple factory with class registration using reflection 34 Simple factory with class registration using Product.newlnstance 35 Factory method pattern 36 Anonymous concrete factory 38 Abstract factory 38 Simple factory versus factory method versus abstract factory 40 Builder pattern 40 Car builder example 41 Simplified builder pattern 43 Anonymous builders with method chaining 44 Prototype pattern 45 Shallow clone versus deep clone Object pool pattern Summary аэоэсБ Chapter 3: Behavioral Patterns
    [Show full text]