singleton | has definition A pattern that ensures that a certain class can have only one instance | ![2001-08-30 14:57:31.0](facet.gif) |
has context | ![2001-08-30 14:57:31.0](facet.gif) |
has example the Company or University classes in systems that run the business of that company or university | ![2001-08-30 14:57:31.0](facet.gif) |
has forces | ![2001-08-30 14:57:31.0](facet.gif) |
has problem How do you ensure that it is never possible to create more than one instance of a singleton class? | ![2001-08-30 14:57:31.0](facet.gif) |
has references one of the Gang of Four patterns. | ![2001-08-30 14:57:31.0](facet.gif) |
has solution In a singleton class, create the following: | ![2001-08-30 14:57:31.0](facet.gif) |
is a subtopic of 6.5 - The Singleton Pattern | ![2001-08-30 14:57:31.0](facet.gif) |
is an instance of design pattern | ![2001-08-30 14:57:31.0](facet.gif) |
design pattern | has antipatterns zero or more antipatterns - solutions that are inferior or do not work in this context with the reason for their rejection | ![2001-08-30 14:55:16.0](facet.gif) |
has name | ![2001-08-30 14:55:16.0](facet.gif) |
has related patterns zero or more related design patterns | ![2001-08-30 14:55:16.0](facet.gif) |
should be illustrated using a simple diagram | ![2001-08-30 14:55:16.0](facet.gif) |
should be written using a narrative writing style | ![2001-08-30 14:55:16.0](facet.gif) |
pattern | should be as general as possible | ![2001-08-30 14:56:56.0](facet.gif) |
should be described in an easy-to-understand form so that people can determine when and how to use it | ![2001-08-30 14:56:56.0](facet.gif) |
should contain a solution that has been proven to effectively solve the problem in the indicated context | ![2001-08-30 14:56:56.0](facet.gif) |