On Tue, Mar 10, 2009 at 12:39 PM, Rickard Öberg <[email protected]> wrote:
> The main problem I see with this is that the UoW would be longrunning, > and since it holds strong references to EntityState/EntityInstances it > will cause memory leaks. This *could* be fixed by using WeakReferences > in the UoW caches but I'm not entirely sure of the consequences of this. Somehow it feels "right", and the memory leak problem is possibly just a caching strategy issue... Having a CachingEntityStore is of course another choice. In either case, don't you need to look at how to deal with cross-JVM synchronizations as well? Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
