For any remote call (which is how all real work is done in our app)
there are two types of things that need to happen:
- Domain logic: updating the model and other stuff related to the
domain / data
- View logic: displaying messages, showing and hiding progress
indicators etc. 

I was thinking of having a responder to handle the Domain logic, and
one for view logic.  Both basically need to know what happened in any
remote call.  So I chain them such that the View asks the Domain Model
to do some domain logic.  In the low level remote service call code we
add these two responders with the Domain Responder first.  Then the
call happens, and it should fire the domain responder then the view
responder.  Either one could send notifications or whatever if there
are other interested parties. 

So questions are:
- Anyone have experience with this kind of pattern?  
- Is this a horrible or good idea? 



Reply via email to