Hi
I am build a large application and have based it around the Comand-Query responsability segregation pattern for a number of reasons (allowing me to segregate the work between developers with lower model-contention and also because the command side triggers some complex actions) but am wondering on the best approach to data-impacting commands.
Currently thinking that the command library should expose a pub-sub notification library that a UI can hook into and listen for messages that tell it "a data impacting thing has occured - you shoud refresh your data". However this violates the "make your UI as dumb as possible" rule.
Any other ideas on how I should do this?
I am build a large application and have based it around the Comand-Query responsability segregation pattern for a number of reasons (allowing me to segregate the work between developers with lower model-contention and also because the command side triggers some complex actions) but am wondering on the best approach to data-impacting commands.
Currently thinking that the command library should expose a pub-sub notification library that a UI can hook into and listen for messages that tell it "a data impacting thing has occured - you shoud refresh your data". However this violates the "make your UI as dumb as possible" rule.
Any other ideas on how I should do this?