Revision as of 01:34, 11 December 2018 edit Cedar101 (talk \| contribs) Extended confirmed users 18,557 edits m →top: plain image for readablity of SVG ← Previous edit		Revision as of 20:30, 12 December 2018 edit undo Garageatrois (talk \| contribs) 80 edits Current phrasing was ambiguous. It made it sound as though the multiton itself was the design pattern which managed single instances, rather than the singleton. Next edit →
Line 1: {{Plain image with caption\|Image:Multiton.svg\|UML diagram of the multiton}} In [[software engineering]], the '''multiton pattern''' is a [[design pattern (computer science)\|design pattern]] ~~similar~~which togeneralizes the [[singleton pattern\|singleton pattern]],. ~~which~~Whereas the [[singleton pattern \| singleton]] allows only one instance of a class to be created., ~~The~~the multiton pattern ~~expands~~allows onfor the ~~singleton~~controlled ~~concept~~creation toof multiple instances, which it manages through the ~~manage~~use a [[associative array\|map]] ~~of named instances as key-value pairs~~. Rather than having a single instance ''per application'' (e.g. the {{Javadoc:SE\|package=java.lang\|java/lang\|Runtime}} object in the [[Java (programming language)\|Java programming language]]) the multiton pattern instead ensures a single instance ''per key''.

Multiton pattern: Difference between revisions