Chain-of-responsibility pattern: Difference between revisions

Revision as of 04:44, 1 February 2005

Revision as of 05:52, 6 March 2005

Line 1:

In [[computer programming]], the '''chain-of-responsibility pattern''' is a [[design pattern (computer science)|design pattern]]s whereconsisting of a source of [[Command pattern|command objects]] areand cominga fromseries somewhere, theirof processing logicobjects. is spreadEach betweenprocessing object contains a numberset of objectslogic andthat describes the commandstypes areof distributed among thosecommand objects. Eachthat objectit iscan smarthandle, enoughand how to knowpass whichoff commandthose objectsthat it cancannot handle,to howthe tonext passprocessing offobject commandin objectsthe itchain. can't handle,A andmechanism howalso toexists addfor adding new processing objects to the end of thethis chain.

'''[[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.