| Mediator |
| Since a Mediator becomes a repository for logic, can the code that implements this logic begin to get overly complex, possible resembling speggheti code? How could this potential problem be solved? |
| Observer |
|
Part 1: The classic Model-View-Controller design is explained in
Implementation note #8: Encapsulating complex update semantics. Would it ever
make sense for an Observer (or View) to talk directly to the Subject (or Model)?
Part 2: What are the properties of a system that uses the Objserver pattern extensively? How would you approach the task of debugging code in such a system? Part 3: Is it clear to you how you would handle concurrency problems with is pattern? Consider an Unregister() message being sent to a subject, just before the subject sends a Notify() message to the ChangeManager (or Controller). |