Chain-of-responsibility pattern: Difference between revisions

Revision as of 00:18, 30 November 2004

Revision as of 08:54, 12 January 2005

Line 1:

In [[computer programming]], '''chain-of-responsibility pattern''' is a [[design pattern (computer science)|design pattern]]s where [[Command pattern|command objects]] are coming from somewhere, their processing logic is spread between a number of objects and the commands are distributed among those objects. Each object is smart enough to know which command objects it can handle, how to pass off command objects it can't handle, and how to add to the end of the chain.

'''Permutations[[Permutation]]s''': Commands may be sent in alternate directions out, forming a tree of [[responsibility]]. Recursion could continue until the command is processed, or the entire tree has been explored. An XML interpreter (parsed, but not yet executed) might be a fitting example.

This pattern promotes the idea of [[loose coupling]], a programming practice.

''The article is originally from [[Perl Design Patterns Book]]''

==See also==

*[[Dependency injection pattern]]

*[[Inversion of Control]]

{{stub}}

[[Category:Software design patterns]]