Question

This is in reference to the ResultObjectPattern.
Usually, the ResultObject will be rather simple with just private instance variables referring to various components of the result, and getter methods (possibly setters too?) for those.

Now, would it be a bad idea to add behavior methods to the ResultObject? For example, let’s say the ResultObject pushed out one or more of its instance variables to a cache and retrieve them back only when needed, or provided methods that do some computation,– would that be okay, or would these be things that’d rather be handled by a separate (singleton/utility) class such as a ResultObjectManager?

Answer 1

I think if behavior is strongly related to data and behavior is not beyond the scope of RO responsibilities – is not bad idea.