Timeline for How to avoid DI dependency cycle for observer pattern
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2023 at 9:41 | answer | added | Eino Gourdin | timeline score: 1 | |
| May 11, 2020 at 8:10 | history | edited | C-Otto | CC BY-SA 4.0 | edited body |
| May 11, 2020 at 0:00 | history | tweeted | twitter.com/StackSoftEng/status/1259634428067942400 | ||
| May 10, 2020 at 19:16 | vote | accept | C-Otto | ||
| May 10, 2020 at 19:02 | comment | added | C-Otto | @BartvanIngenSchenau Autowiring is dependency injection provided by the container, similar to @Inject in JavaEE environments. And yes, each observer may be provided to multiple subjects: EmitsSomething could be a concrete Subject, and Y implements ReceivesSomething, ReceivesSomethingElse might be an observer for this subject that also observes notifications from another subject. | |
| May 10, 2020 at 18:19 | comment | added | Bart van Ingen Schenau | I am not familiar with autowiring. Can you have X classes being a Subject and Y classes being an Observer, where each Observer receives notifications from a different set of Subjects? Because that is a very common usecase for the Observer pattern (multiple instances of the pattern all over the codebase). | |
| May 10, 2020 at 17:59 | answer | added | joakim | timeline score: 1 | |
| May 10, 2020 at 15:34 | answer | added | candied_orange | timeline score: 1 | |
| May 10, 2020 at 13:36 | history | asked | C-Otto | CC BY-SA 4.0 |