Re: [Xorm-devel] Distributed Cache Management

[Wes B. <we...@ca...>]

Harry Evans wrote:

> For objects that have been seen, but are not currently locked, txnId 
> and expires would be null.  For objects that are locked, all values 
> would be non null.  Locks can be removed lazily, by checking a lock 
> when needed, and if it is expired, nulling txnId and expires.

It's OK for the lock manager to not keep strong references to every 
object it has seen, right?

Also, should the lock manager be informed of newly persisted objects 
(i.e. creates) or is it only concerned with updates?  I think it's the 
latter but wanted to make sure I was understanding the whole scheme.

Some good news for caching in general -- JDO 2.0 will provide a 
PersistenceManagerFactory.getDataStoreCache() method that can be used to 
pin or evict objects, extents, or all cached data.

I think the next thing to document (again, in PDF would be best) is the 
full interaction diagram between a user-level transaction, XORM's 
DataCache (LRUCache) and the LockManager.

Wes