|WikiProject Computing / Software||(Rated Start-class)|
Please correct the example. The current example misses the point of both the mediator pattern and loose coupling. The point is to send logical events (like contentUpdated) to the mediatior, which passes them on to all the other listeners. It's not necessary to have a simple message queue as in the example - there can and often there should be logic in handling the events as well. The point is that this logic is in one place only.
The link to Mediator Pattern in Java is broken :-(
Uml show a diamond
Uml show an ugly diamond iheritance diagram. That is dirty in developpment design.
Which of ConcreateColleagueA or ConcreateColleagueB members, ConcreateMediator must inherit ????????
Yep, the UML is wrong
The concrete mediator should have an association relationship (arrow) to the concrete colleagues; the diagram shows an inheritance (triangle). —Preceding unsigned comment added by 126.96.36.199 (talk) 00:00, 22 September 2008 (UTC)
Article desperately needs improvement
The current version of the article needs an overhaul. The example is way too long and contains a lot of information that is not related with the mediator pattern at all. Also some kind of diagram is missing. The article about the Observer pattern can be a guideline as it describes with less words much better what a pattern is and how it works. --Vario (talk) 17:38, 22 March 2012 (UTC)