Code review comment for lp:~free.ekanayaka/storm/infoheritance

I still don't understand your view. Specifically, I don't get whether you are suggesting to not use the infoheritance pattern at all by arranging your model objects differently, OR to use it but implement it with the non-fancy no-magic way described in the Storm website in the infohertiance page.

What I think is that if we are fine with the infoheritance pattern, or we don't have really sound alternatives (as it's the case with Landscape atm, since we are still using that pattern), then I believe there's nothing too bad in implementing support for it in Storm, which at the end of the day just move the very same non-fancy no-magic user code/logic into Storm, for convenience and sake of code re-use.