Timeline for Information sharing in event-based systems
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2018 at 11:02 | audit | Suggested edits | |||
| Jan 5, 2018 at 11:05 | |||||
| Jan 4, 2018 at 6:42 | history | tweeted | twitter.com/StackSoftEng/status/948806946852954113 | ||
| Dec 18, 2017 at 7:44 | comment | added | S.D. | Both of your concerns may actually become a big issue because of one primary reason: Modules are not truly separated, they need each other's data and ask each other for confirmation to do their own work. Minimize that and you've got a well decoupled system. | |
| Dec 16, 2017 at 20:13 | answer | added | Robert Bräutigam | timeline score: 2 | |
| Dec 16, 2017 at 19:18 | review | Close votes | |||
| Jan 4, 2018 at 3:03 | |||||
| Dec 16, 2017 at 19:16 | answer | added | Vadim Samokhin | timeline score: 2 | |
| Dec 16, 2017 at 18:46 | review | First posts | |||
| Dec 17, 2017 at 2:39 | |||||
| Dec 16, 2017 at 18:45 | comment | added | Slava Fomin II | @Zapadlo the module is a directory with code related to some specific and isolated feature of the application. The module could interface with the core's API and react to some events, effectively enhancing/altering the application behavior. The module could provide it's own entities, request controllers, CLI commands among other things. | |
| Dec 16, 2017 at 18:42 | comment | added | Vadim Samokhin | What do you understand by modules? | |
| Dec 16, 2017 at 18:39 | history | asked | Slava Fomin II | CC BY-SA 3.0 |