Results 1 to 5 of 5

Thread: Command-Query responsability segregation and change notification

Threaded View

  1. Mar 24th, 2013, 02:50 PM #1
    Merrion
    Merrion is offline

    Thread Starter
    PowerPoster
    Join Date
    Jul 2002
    Location
    Dublin, Ireland
    Posts
    2,148

    Command-Query responsability segregation and change notification

    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?
    Last edited by Merrion; Mar 24th, 2013 at 02:53 PM. Reason: better info link
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules


Click Here to Expand Forum to Full Width