Message traffic (what I do)
Str#113. "Batch Up Immediate Results" Strategy
- Excess message traffic can make an object model harder to
understand and harder to implement, too.
- Here's what to do about it: "Batch up" immediate results.
Add attributes that hold intermediate results, to reduce
message traffic. In effect, you are moving a repeated
calculation "outside of the (iteration) loop." A classic
example: adding a "total" attribute along with a "calcTotal"
service.
Str#114. "Traveling Object" Strategy
- Pass an object (or object ID) as a parameter, allowing it
to travel along a series of message sends. At the end of the
series, the last object can send the result directly to the
originator (a short cut, rather than waiting for all the
message sends to work back to the originator. (The caller - dispatcher - caller-back
pattern is a good example of this.)
Str#115. "Sender, Intermediary, Receiver" Strategy
Establishing responsibilities
/ what I do
Strategies for building object
models