GoF之Singleton 单例模式

资料出处：staruml 转载请说明出自StarUML

Singleton

• Purpose
• Structure
• Applications
• Consequences

Purpose

• Ensure a class only has one instance, and provide a global point of access to it.

Structure

 

• Singleton: defines an Instance operation that lets clients access its unique instance. Instance is a class operation (that is, a class method in Smalltalk and a static member function in C++).
  may be responsible for creating its own unique instance.

Applications

• there must be exactly one instance of a class, and it must be accessible to clients from a wellknown access point.
• when the sole instance should be extensible by subclassing, and clients should be able to use an extended instance without modifying their code.

Consequences

• Controlled access to sole instance. Because the Singleton class encapsulates its sole instance, it can have strict control over how and when clients access it.
• Reduced name space. The Singleton pattern is an improvement over global variables. It avoids polluting the name space with global variables that store sole instances.
• Permits refinement of operations and representation. The Singleton class may be subclassed, and it's easy to configure an application with an instance of this extended class. You can configure the application with an instance of the class you need at run-time.
• Permits a variable number of instances. The pattern makes it easy to change your mind and allow more than one instance of the Singleton class. Moreover, you can use the same approach to control the number of instances that the application uses. Only the operation that grants access to the Singleton instance needs to change.