What is the chain of responsibility?

The

liability string (COR) includes the process of marking the activities and responsibilities of each entity in an object -oriented design pattern. There are two basic elements in the object -oriented design; command objects and processing objects. Command objects generate commands for processing objects and process processing objects from commands that can process and pass the rest to others in the string. This is a basic principle in an object -oriented design and the design is much greater flexibility, such as the new object cover at any point in the design pattern of the responsibility chain. There is a string of different objects that are aligned for processing commands, and if one cannot handle it, it can pass it over in the chain. The liability string continues to continue until one of the objects is accepted.

The

liability string must be more flexible and support the addition of new operators in the chain. ForAs every handler is unable to perform every task, there must be a group of operators that can work collectively. The chain of responsibility could be some disadvantages, as some commands remain unresolved, even at the end of the string. To solve this problem, one of the solutions is to implement all operators for all possible requirements.

There could be some problems related to broken links in the liability chain system. If the programmer forgets to connect commands, the request may be lost. The representation of the application is significant because it is used in all components of the responsibility chain. Another That That may be in the design COR is that some problems in the concrete service may be completely unaddited at the end of the chain. Overall, however, the chain of responsibility is a good system to implement if it has been carefully designed, with regard to all related aspects.