Middle man smell

From CSSEMediaWiki

Jump to: navigation, search

In object oriented programming, it is common to delegate some work to other objects. However, if a class delegates the majority of work to another class, it is just a middle man and should be removed. Instead, you should talk directly to the class that implements the behavior rather than going through the middle man.

Conflicts

Mediator can turn into a middle man that does little other than delegating to other objects.
Facade by definition delegates to classes in a subsystem that is being hidden from other parts of the system.

See also

Code smells

Class Level: Alternative classes with different interfaces smell | Data class smell | Data clumps smell | Divergent change smell | Duplicate code smell | Inappropriate intimacy smell | Incomplete library class smell | Large class smell | Lazy class smell | Message chain smell | Middle man smell | Parallel inheritance hierarchies smell | Primitive obsession smell | Refused bequest smell | Shotgun surgery smell | Speculative generality smell | Temporary field smell

Method Level: Comments smell | Feature envy smell | Long method smell | Long parameter list smell | Switch statement smell

Retrieved from "https://oowisdom.csse.canterbury.ac.nz/index.php?title=Middle_man_smell&oldid=9252"

Code smells

Views

Personal tools

Log in / create account

Search

Toolbox