On 2010-10-04 10.59, Niclas Hedhman wrote:
As I said previously, caching the EnityState with copy-on-write is a
much more complex undertaking, as there are many locations where the
EntityState are held. I agree we should look into this later, BUT I
think this time is not the moment to try and get copy-on-write done
and wait with the whole thing post-1.2
Likely is that the EntityState references needs to include an
additional indirection level, so the EntityState instance can be
replaced in one spot, AND ensure that nothing caches the values
elsewhere.
Not quite sure I understand this. Each EntityState is only by one UoW
only, so if you just include a boolean "copied" which is default false,
and then check it on set's, and copy the underlying JSON-object before
modifying it, that should be it, AFAICT.
Am I missing something?
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
