Chain-of-responsibility pattern: Difference between revisions

Revision as of 17:23, 28 December 2021

Revision as of 13:53, 26 January 2022

Line 14:

that describe common solutions to recurring design problems when designing flexible and reusable object-oriented software, that is, objects that are easier to implement, change, test, and reuse.

<big>===What problems can the Chain of Responsibility design pattern solve?</big>===

<ref>{{cite web|title=The Chain of Responsibility design pattern - Problem, Solution, and Applicability|url=http://w3sdesign.com/?gr=b01&ugr=proble|website=w3sDesign.com|access-date=2017-08-12}}</ref>

* Coupling the sender of a request to its receiver should be avoided.

Line 22:

because it couples the class to a particular receiver and makes it impossible to support multiple receivers.

<big>===What solution does the Chain of Responsibility design pattern describe?</big> ===

* Define a chain of receiver objects having the responsibility, depending on run-time conditions, to either handle a request or forward it to the next receiver on the chain (if any).