Hey Sergio,
My only concern with that is that LockableMap touches a lot of public
(and private) stuff across tim-concurrent-collections, tim-distributed-
cache, tim-hibernate-cache, etc:
ConcurrentDistributedMap, ConcurrentStringMap,
ConcurrentDistributedMapBackend (and it's subclasses)
DistributedCache (and impl), LocalCache (and store), CacheStore, etc
So I hesitate to add this without some thought. I'm not against
adding a tryLockEntry() and we actually have a jira for that already:
http://jira.terracotta.org/jira/browse/CDV-1422
Maybe it would be better to add it just to ConcurrentDistributedMap
directly and not LockableMap for the moment?
On Nov 11, 2009, at 2:53 AM, Sergio Bossa wrote:
Hi guys,
is it possible to add a tryLockEntry(...) method to LockableMap so
that it could be called from ConcurrentDistributedMap instances?
I could handle the patch by myself, if you agree with it.
Thanks,
Cheers,
Sergio B.
--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-forge-dev mailing list
tc-forge-...@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-forge-dev
_______________________________________________
tc-dev mailing list
tc-dev@lists.terracotta.org
http://lists.terracotta.org/mailman/listinfo/tc-dev
