1 / 14

To Kill a Singleton Factory Method Pattern

To Kill a Singleton Factory Method Pattern. Josh Mason 6/18/09. To Kill a Singleton. Will try and answer these important questions Who deletes a singleton? How do you go about deleting a singleton?. Original Design. Recall Single Instance of a class Class controls its own creation

navid
Télécharger la présentation

To Kill a Singleton Factory Method Pattern

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. To Kill a SingletonFactory Method Pattern Josh Mason 6/18/09

  2. To Kill a Singleton • Will try and answer these important questions • Who deletes a singleton? • How do you go about deleting a singleton?

  3. Original Design • Recall • Single Instance of a class • Class controls its own creation • Not addressed • Destructors • Deletion/Cleanup • Key ideas to keep in mind • Destruction order • Dangling references • Singletons typicallylong lived

  4. Possible Solutions • Explicit destruction • *Singleton destroyer • *Static function variable

  5. Singleton Destroyer • Static object in Singleton class • Manages singleton instance • Automagically cleans up Singleton class on program exit • Consequences • Order of static object destruction undefined (in C++) • Requires use of friend keyword to access protected instance • Only cleaned up on process termination

  6. Static Function Variable • Declare instance variable in Instance() as static • Return reference to instance variable • Automagically cleans up Singleton class on program exit • Consequences • Don’t need SingletonDestroyer • Uses object notation instead of dereference notation (. vs -> in C++) • Still doesn’t solve order singletons with mutual dependency • Only cleaned up on process termination

  7. Factory Method Pattern • Creational Pattern • Defines interface for creation of objects, but lets subclasses decide which class to instantiate • Defers instantiation to subclasses • Commonly used to “refer to any method whose main purpose is creation of objects”

  8. Applicability • Use the Factory Method Pattern when • A class can’t anticipate the class of objects it must create • A class wants its subclasses to specify the object it creates • Classes delegate responsibility to one of several helper subclasses, and you want to localize the knowledge of which helper subclass is the delegate.

  9. Class Diagram

  10. Participants • Product • Defines product interface • Concrete Product • Implements Product interface • Creator • Declares FactoryMethod() • May call FactoryMethod() to create object • Concrete Creator • Overrides FactoryMethod() to return an instance of Concrete Product

  11. Consequences • Provides hooks for subclasses • Eliminates the need to bind application-specific classes into code. • Enables the subclasses to provide an extended version of an object • Connects parallel class hierarchies

  12. Example

  13. Considerations on Implementation • Two major varieties • Creator is abstract and provides no default implementation • Creator is concrete and provides default implementation • Parameterized factory methods • Use of templates to avoid subclassing • Name factory method appropriately

  14. Related Patterns • Abstract Factory • Template Method • Defers some steps to children. Specifically creation of object • Prototype • Doesn’t require subclassing Creator. Often require Initialize operation on Product class which Factory Method doesn't require.

More Related