Guus Bloemsma wrote:
Not in the persistence layer itself. If the client would load all entities it needed by itself it would do a roundtrip for each entity or set of entities. It is more performant if the server preloads everything that will be needed and sends it off at once. Unfortunately this requires some knowledge of what the client might do with those entities.
This we can do by dynamic analysis of what the usecases load. This is a MAJOR difference between Qi4j and other frameworks: for each usecase we can specify its name and attributes, and this can then be used by the infrastructure. So, when the client starts a UoW with a Usecase on the client, and that UoW calls the server, the server can be given the name of the usecase and then return more state than the client asked for, since it can know that it will be necessary later in that usecase. I have implemented this kind of strategy before, so I know its doable, and here we have all the metainfo we need to do it properly!
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
