Timeline for Design pattern recommendation for chain-of-responsibility with task delegation
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 20, 2017 at 22:52 | comment | added | ZeroOne | Have you looked into using the Visitor Pattern instead? | |
| Aug 13, 2017 at 20:35 | history | edited | instanceOfObject | CC BY-SA 3.0 | added 12 characters in body |
| Aug 12, 2017 at 14:31 | comment | added | Filip Milovanović | The Chain of Responsibility pattern is not necessarily the best choice here; it's good when you already have a structure that is chain-like or hierarchical. (E.g., consider custom GUI controls - a window contains a panel, which contains a button. The user clicks the button, but its the window that receives the mouse event, and then forwards it down to the descendant controls until one of them handles it.) But here, it looks like you are imposing the chain structure artificially. Maybe you can simply use a Factory to create an instance of a concrete type depending on your conditions? | |
| Aug 12, 2017 at 3:52 | answer | added | candied_orange | timeline score: 1 | |
| Aug 12, 2017 at 3:06 | comment | added | candied_orange | An example of how you intend to use this code would help. | |
| Aug 12, 2017 at 3:02 | history | edited | candied_orange | CC BY-SA 3.0 | Simplifying verbage |
| Aug 12, 2017 at 1:58 | comment | added | candied_orange | The I for interface prefix thing you use in IFace is a c# thing not a Java thing and certainly not a good thing. Please limit its use to c#. | |
| Aug 12, 2017 at 0:16 | comment | added | Derek Elkins left SE | Following (design) patterns is not a goal. | |
| Aug 12, 2017 at 0:08 | history | asked | instanceOfObject | CC BY-SA 3.0 |