“Prototype pattern”的意思、由来-开放百科全书

词条 Prototype pattern

释义

Overview
Structure
UML class and sequence diagram UML class diagram
Rules of thumb
Pseudocode
C# Example
Java Example
PHP Example
See also
References
Sources

{{Refimprove|date=November 2014}}{{other uses|Software prototyping}}{{distinguish|Prototype-based programming|Function prototype}}

The prototype pattern is a creational design pattern in software development. It is used when the type of objects to create is determined by a prototypical instance, which is cloned to produce new objects. This pattern is used to:

avoid subclasses of an object creator in the client application, like the factory method pattern does.
avoid the inherent cost of creating a new object in the standard way (e.g., using the 'new' keyword) when it is prohibitively expensive for a given application.

To implement the pattern, declare an abstract base class that specifies a pure virtual clone() method. Any class that needs a "polymorphic constructor" capability derives itself from the abstract base class, and implements the clone() operation.

The client, instead of writing code that invokes the "new" operator on a hard-coded class name, calls the clone() method on the prototype, calls a factory method with a parameter designating the particular concrete derived class desired, or invokes the clone() method through some mechanism provided by another design pattern.

The mitotic division of a cell — resulting in two identical cells — is an example of a prototype that plays an active role in copying itself and thus, demonstrates the Prototype pattern. When a cell splits, two cells of identical genotype result. In other words, the cell clones itself.{{refn|{{cite journal |last1=Duell |first1=Michael |title=Non-Software Examples of Design Patterns |journal=Object Magazine |volume=7 |issue=5 |date=July 1997 |pages=54 |issn=1055-3614}}}}

Overview

The Prototype

^[1]

design pattern is one of the twenty-three well-known

GoF design patterns

that describe how to solve recurring design problems to design flexible and reusable object-oriented software, that is, objects that are easier to implement, change, test, and reuse.

The Prototype design pattern solves problems like:^[2]

How can objects be created so that which objects to create can be specified at run-time?
How can dynamically loaded classes be instantiated?

Creating objects directly within the class that requires (uses) the objects

is inflexible because it commits the class to particular objects at compile-time and makes it impossible to specify which objects to create at run-time.

The Prototype design pattern describes how to solve such problems:

Define a Prototype object that returns a copy of itself.
Create new objects by copying a Prototype object.

This enables configuration of a class with different Prototype objects, which are copied to create new objects, and even more, Prototype

objects can be added and removed at run-time.

See also the UML class and sequence diagram below.

Structure

UML class and sequence diagram

In the above UML class diagram,

the Client class that requires a Product object doesn't instantiate the Product1 class directly.

Instead, the Client refers to the Prototype interface for cloning an object.

The Product1 class implements the Prototype interface by creating a copy of itself.

The UML sequence diagram shows the run-time interactions:

The Client object calls clone() on a prototype:Product1 object, which creates and returns a copy of itself (a product:Product1 object).

UML class diagram

Rules of thumb

Sometimes creational patterns overlap — there are cases when either prototype or abstract factory would be appropriate. At other times they complement each other: abstract factory might store a set of prototypes from which to clone and return product objects (GoF, p126). Abstract factory, builder, and prototype can use singleton in their implementations. (GoF, p81, 134). Abstract factory classes are often implemented with factory methods (creation through inheritance), but they can be implemented using prototype (creation through delegation). (GoF, p95)

Often, designs start out using Factory Method (less complicated, more customizable, subclasses proliferate) and evolve toward abstract factory, prototype, or builder (more flexible, more complex) as the designer discovers where more flexibility is needed. (GoF, p136)

Prototype does not require subclassing, but it does require an "initialize" operation. Factory method requires subclassing, but does not require initialization. (GoF, p116)

Designs that make heavy use of the composite and decorator patterns often can benefit from Prototype as well. (GoF, p126)

The rule of thumb could be that you would need to clone() an Object when you want to create another Object at runtime that is a true copy of the Object you are cloning. True copy means all the attributes of the newly created Object should be the same as the Object you are cloning. If you could have instantiated the class by using new instead, you would get an Object with all attributes as their initial values.

For example, if you are designing a system for performing bank account transactions, then you would want to make a copy of the Object that holds your account information, perform transactions on it, and then replace the original Object with the modified one. In such cases, you would want to use clone() instead of new.

Pseudocode

Let's write an occurrence browser class for a text. This class lists the occurrences of a word in a text. Such an object is expensive to create as the locations of the occurrences need an expensive process to find. So, to duplicate such an object, we use the prototype pattern:

 '''class''' WordOccurrences '''is'''   '''field''' occurrences '''is'''     The list of the index of each occurrence of the word in the text.    '''constructor''' WordOccurrences(text, word) '''is'''       '''input:''' the ''text'' in which the occurrences have to be found       '''input:''' the ''word'' that should appear in the text     Empty the ''occurrences'' list     '''for each''' textIndex '''in''' text       isMatching := true       '''for each''' wordIndex '''in''' word         '''if''' the current word character does not match the current text character '''then'''           isMatching := false       '''if''' isMatching is true '''then'''         Add the current textIndex into the ''occurrences'' list    '''method''' getOneOccurrenceIndex(n) '''is'''       '''input:''' a number to point on the ''n''th occurrence.       '''output:''' the index of the ''n''th occurrence.     Return the ''n''th item of the ''occurrences'' field if any.    '''method''' clone() '''is'''       '''output:''' a WordOccurrences object containing the same data.     Call clone() on the super class.     On the returned object, set the ''occurrences'' field with the value of the local ''occurrences'' field.     Return the cloned object.  text := "The prototype pattern is a creational design pattern in software development first described in design patterns, the book." word := "pattern"d searchEngine := new WordOccurrences(text, word) anotherSearchEngine := searchEngine.clone()

(the search algorithm is not optimized; it is a basic algorithm to illustrate the pattern implementation)

C# Example

This pattern creates the kind of object using its prototype. In other words, while creating the object of Prototype object, the class actually creates a clone of it and returns it as prototype.You can see here, we have used MemberwiseClone method to clone the prototype when required.

public abstract class Prototype

{

}

public class ConcretePrototype1 : Prototype

{

    public override Prototype Clone()    {        return (Prototype)this.MemberwiseClone(); // Clones the concrete class.    }

}

public class ConcretePrototype2 : Prototype

{

    public override Prototype Clone()    {        return (Prototype)this.MemberwiseClone(); // Clones the concrete class.    }

}

Java Example

This pattern creates the kind of object using its prototype. In other words, while creating the object of Prototype object, the class actually creates a clone of it and returns it as prototype. You can see here, we have used Clone method to clone the prototype when required.

// Prototype pattern

public abstract class Prototype implements Cloneable {

    public Prototype clone() throws CloneNotSupportedException{        return (Prototype) super.clone();    }

}

public class ConcretePrototype1 extends Prototype {

    @Override    public Prototype clone() throws CloneNotSupportedException {        return (ConcretePrototype1)super.clone();    }

}

public class ConcretePrototype2 extends Prototype {

    @Override    public Prototype clone() throws CloneNotSupportedException {        return (ConcretePrototype2)super.clone();    }

}

PHP Example

// The Prototype pattern in PHP is done with the use of built-in PHP function __clone()

abstract class Prototype

{

    public $a;    public $b;        public function displayCONS()    {        echo "CONS: {$this->a}\";        echo "CONS: {$this->b}\";    }        public function displayCLON()    {        echo "CLON: {$this->a}\";        echo "CLON: {$this->b}\";    }

}

class ConcretePrototype1 extends Prototype

{

    public function __construct()    {        $this->a = "A1";        $this->b = "B1";                $this->displayCONS();    }

    function __clone()    {        $this->displayCLON();    }

}

class ConcretePrototype2 extends Prototype

{

    public function __construct()    {        $this->a = "A2";        $this->b = "B2";                $this->displayCONS();    }

    function __clone()    {        $this->a = $this->a ."-C";        $this->b = $this->b ."-C";                $this->displayCLON();    }

}

$cP1 = new ConcretePrototype1();

$cP2 = new ConcretePrototype2();

$cP2C = clone $cP2;

// RESULT: #quanton81

// CONS: A1

// CONS: B1

// CONS: A2

// CONS: B2

// CLON: A2-C

// CLON: B2-C

References

1. ^{{cite book|author=Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides|title=Design Patterns: Elements of Reusable Object-Oriented Software|year=1994|publisher=Addison Wesley|isbn=0-201-63361-2|pages=117ff}}
2. ^{{cite web|title=The Prototype design pattern - Problem, Solution, and Applicability|url=http://w3sdesign.com/?gr=c04&ugr=proble|website=w3sDesign.com|accessdate=2017-08-17}}

Sources

{{cite book

|last1=Gamma |first1=Erich |authorlink1=Erich Gamma |last2=Helm |first2=Richard |last3=Johnson |first3=Ralph |authorlink3=Ralph Johnson (computer scientist) |last4=Vlissides |first4=John |authorlink4=John Vlissides
|title=Design Patterns: Elements of Reusable Object-Oriented Software |titlelink=Design Patterns
|publisher=Addison-Wesley
|year=1994
|isbn=0-201-63361-2
}}{{Design Patterns Patterns}}

2 : Software design patterns|Articles with example Java code

随便看

开放百科全书收录14589846条英语、德语、日语等多语种百科知识，基本涵盖了大多数领域的百科知识，是一部内容自由、开放的电子版国际百科全书。