It seems to me you are trying to find a commonality and then extrapolate from there what's the best approach. But there is none. That's simply not the best way to evaluate the need for one over the other.Originally Posted by audinue
The approach has to be defined on a case by case basis. And even then, what might be a desirable approach in terms of performance or resource usage, may not be in terms of code maintainability or expansibility, or vice-versa, or in any other combination. Meaning, more often than not you are left with a paradigm you need to resolve. And the best option can often be described as "Pick your favorite poison".
