On Mon, Mar 5, 2012 at 11:43 AM, Rickard Öberg <[email protected]> wrote:
Good Stuff as usual... > In other words, what exists in memory is a REPRESENTATION of the "object", > rather than "The Object" proper. Like in REST, you can never see the object > "as it is", only through views. I kinda like this, conceptually, and if we > could support this in Qi4j explicitly, it'd be awesome. > Can we do that? I don't know! We have not been afraid to set the bar high before, so why stop now. Doesn't it "only" boils down to additional Entity Store SPI information dividing up the data chunks across roles? If I store a "Person" and then retrieve an "Employee", only the overlapping data (same Method accessor type) will be part of the Employee of the same UUID, which can then be populated with yet additional information, without destroying the Person content that wasn't loaded. I.e. namespace separation but with namespace inheritance. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/6a2pl4j I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
