Scribd
Upload
46 views9 pages

Mediator

The Mediator pattern promotes loose coupling between classes by having a mediator class that coordinates communication between other classes known as colleagues. The mediator has knowledge of the methods of colleague classes and passes information between them when changes occur. This prevents classes from having direct references to each other, reducing complexity and making the program easier to read, maintain, and change.

Uploaded by

srianjaneyam0078297
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
46 views9 pages

Mediator

The Mediator pattern promotes loose coupling between classes by having a mediator class that coordinates communication between other classes known as colleagues. The mediator has knowledge of the methods of colleague classes and passes information between them when changes occur. This prevents classes from having direct references to each other, reducing complexity and making the program easier to read, maintain, and change.

Uploaded by

srianjaneyam0078297
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 9

Mediator Pattern Intro

If a program is composed of a number of classes, the logic and


computation is divided logically among these classes.
- The communication between the classes is very complex
The more each class needs to know about the methods of another class,
the more tangled the class structure can become.
- This makes the program harder to read and harder to maintain & also
difficult to change the program, since any change may affect code in
several other classes.
The Mediator pattern addresses this problem by promoting looser
coupling between these classes.
Mediators accomplish this by being the only class that has detailed
knowledge of the methods of other classes.
Classes send information to the mediator when changes occur and the
Mediator passes them on to any other classes that need to be informed.
Mediator Intention
• Defines an object that encapsulates how a
set of objects interact.
o promotes loose coupling by keeping objects
from referring to each other explicitly
o lets vary their interaction independently
Motivation
• Example:
Mediator importance

Before After
Applicability
• A set of objects communicate in a well-
defined but complex manner
• Reusing an object is difficult because it
refers to and communicates with many
other objects
• A behavior that's distributed between
several classes should be customizable
without a lot of subclassing
Structure

• Mediator
o defines an interface for communicating with Colleague objects
• ConcreteMediator
o knows and maintains its colleagues
o implements cooperative behavior by coordinating Colleagues
• Colleague classes
o each Colleague class knows its Mediator object
o each colleague communicates with its mediator whenever it would
have otherwise communicated with another colleague
Object Structure
Consequences
1. Loose coupling between objects in program.
2. Change the behavior of the program by simply changing
or sub classing the Mediator.
3. Add new Colleagues to a system without having to
change any other part of the program.
4. Mediator solves the problem of each Command object
needing to know too much about the objects and
methods in the rest of a user interface.
5. The Mediator can become monolithic in complexity,
making it hard to change and maintain.
6. Difficult to reuse as Each Mediator is a custom-written
class that has methods for each Colleague to call and
knows what methods each Colleague has available.
Implementations
1. The Mediator pattern we have described above acts as
a kind of Observer pattern, observing changes in the
Colleague elements.
2. Omitting abstract mediator class.
3. Another approach is to have a single interface to
Mediator, and pass that method various constants or
objects which tell the Mediator which operations to
perform.
4. In the same fashion, we could have a single Colleague
interface that each Colleague would implement, and
each Colleague would then decide what operation it was
to carry out.
5. Mediators are not limited to use in visual interface
programs, we can use whenever complex
intercommunication between a number of objects.

You might also like