Content deleted Content added
Dryingpole (talk | contribs) fix citations |
Dryingpole (talk | contribs) add dispersed control style definition |
||
Line 161:
=====When to use=====
When you want to delegate work to objects that are more specialized.
====Dispersed Control Style====
A dispersed control style does not contain any control centers. The logic is spread across the entire population of objects, keeping each object small and building in as few dependencies among them as possible<ref name="ObjectDesign-page30">{{harvnb |Wirfs-Brock|McKean|2002| pp=30 }}</ref>.
=====Advantages=====
* None
=====Disadvantages=====
* When you want to find out how something works, you must trace the sequence of requests for services across many objects
* Not very reusable because no single object contributes much
=====When to use=====
Never.
====Preferred Control Style====
The inventors of Responsibility-Driven Design recommend using a delegated control style because no one object knows or does too much<ref name="ObjectDesign-page133">{{harvnb |Wirfs-Brock|McKean|2002| pp=133 }}
==Conflict with the law of Demeter==
| |||