Difference between revisions of "Chain of Responsibility"
| Line 2: | Line 2: | ||
[[Image:CoR1.jpg]] | [[Image:CoR1.jpg]] | ||
| + | |||
---- | ---- | ||
== Purpose == | == Purpose == | ||
* Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it. | * Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it. | ||
| + | |||
---- | ---- | ||
== UML Diagram == | == UML Diagram == | ||
| + | |||
[[Image:CoR_UML.jpg]] | [[Image:CoR_UML.jpg]] | ||
| Line 19: | Line 22: | ||
---- | ---- | ||
| + | |||
| + | |||
--[[User:Djeyarat|Djeyarat]] 15:49, 2 April 2007 (EDT) | --[[User:Djeyarat|Djeyarat]] 15:49, 2 April 2007 (EDT) | ||
Revision as of 14:51, 2 April 2007
- The Chain of Responsibility pattern uses a chain of objects to handle a request, which is typically an event. Objects in the chain forward the request along the chain until one of the objects handles the event. Processing stops after an event is handled.
Purpose
- Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.
UML Diagram
External Links
- External Links
--Djeyarat 15:49, 2 April 2007 (EDT)
