Timeline for How to handle state of an object? And how to enrich the state transition logic?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2018 at 11:49 | comment | added | FranMowinckel | @Creepin Yep exactly +1. The point is that the ILoginService just handle the procedure but doesn't know the state, so let someone else to manage it (this relates to SRP, right?). That's if preventing 2× login is really needed. This is only a way to do that. | |
| Sep 16, 2018 at 7:49 | comment | added | Creepin | I also thought about that. It tracks down to Christophes second idea I think. Being an observer to some observant. But ILoginState must also be notified by ILoginService about state changes. While ILoginState could be implemented specifically for the system (listening to logins and to resets or only to logins) I feel a bit bad about reacting to an implementation detail in a (base) class. What if I got to know this behavior 2 weeks later and designed and implemented the ILoginService under normal circumstances? | |
| Sep 15, 2018 at 21:42 | history | answered | FranMowinckel | CC BY-SA 4.0 |