|
Mar
9 |
|
awarded | Popular Question |
|
Feb
19 |
|
awarded | Enthusiast |
|
Jan
10 |
|
revised |
DDD - Invalidating expirable added 9 characters in body |
|
Jan
10 |
|
revised |
DDD - Invalidating expirable added 9 characters in body |
|
Jan
10 |
|
accepted | DDD - Invalidating expirable |
|
Jan
10 |
|
answered | DDD - Invalidating expirable |
|
Jan
10 |
|
revised |
DDD - Invalidating expirable added 430 characters in body |
|
Jan
9 |
|
comment |
DDD - Invalidating expirable Cheers :) Read it again and found another good explanation of invariants: devlicio.us/blogs/casey/archive/2009/03/11/… |
|
Jan
8 |
|
revised |
DDD - Invalidating expirable deleted 42 characters in body |
|
Jan
8 |
|
revised |
DDD - Invalidating expirable deleted 15 characters in body; edited title |
|
Jan
8 |
|
comment |
DDD - Invalidating expirable I see. Thanks for the explanation. I didn't know that, do you know where I can find that in the big blue of Evans? :) |
|
Jan
8 |
|
comment |
DDD - Invalidating expirableUser is the T. So User is the aggregate which maintains the enforcements of adding/removing/updating invariants (IEnumerable<Expirable<UserSession>>). Correct?
|
|
Jan
8 |
|
revised |
DDD - Invalidating expirable added 1 characters in body |
|
Jan
8 |
|
comment |
DDD - Invalidating expirable See my comment below for a example gist. |
|
Jan
8 |
|
revised |
DDD - Invalidating expirable added 54 characters in body |
|
Jan
7 |
|
comment |
DDD - Invalidating expirable That's correct indeed! I thought of that later when I was working on my InvalidateExpirable method (see above). I could refactor the "query" part out of that method into a specification. Makes the domain more elegant and expressive. I might do that later, but for now it's sufficient. Querying is not really the problem, the problem is where and when and to remove the invariants (performance wise this could be a issue I guess). Every time you fire up a Repository or at each method in the repository which returns data? (would be more error-prone) |
|
Jan
5 |
|
revised |
DDD - Invalidating expirable added 12 characters in body |
|
Jan
5 |
|
answered | DDD - Invalidating expirable |
|
Jan
5 |
|
comment |
DDD - Invalidating expirable Interesting thought, haven't thought of that! :) I've read the chapter about specifications. The problem with this solution is that you will have to load the complete NotExpired set in memory, not very efficient. On the flipside it opens some idea's to me to try out. |
|
Jan
4 |
|
revised |
DDD - Invalidating expirable deleted 3 characters in body |
