network profile
| bio | website | |
|---|---|---|
| location | Kansas | |
| age | 40 | |
| visits | member for | 11 months |
| seen | Jul 30 '12 at 14:18 | |
| stats | profile views | 1 |
Just enjoying the weird and wonderful world of software development.
|
Jul 3 |
awarded | Supporter |
|
Jul 3 |
comment |
Validation and authorization in layered architecture +1 for authorization - putting it in the UI is an alternative that I did not mention in my answer. |
|
Jul 2 |
comment |
Validation and authorization in layered architecture I have edited my answer - see if this helps. As for " where would you apply the rules in the given model?"; probably around 4, 5, 6, 7 in your command handler. You have access to the repositories that can yield the information you need to perform business level validation. But I think there are others that would disagree with me here. |
|
Jul 2 |
awarded | Editor |
|
Jul 2 |
revised |
Validation and authorization in layered architecture adding more detail per request from original poster |
|
Jun 14 |
awarded | Teacher |
|
Jun 14 |
answered | Validation and authorization in layered architecture |
