On Wed, Nov 11, 2009 at 4:20 PM, Alex Miller <amil...@terracottatech.com> wrote:
> 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: I see your concerns ... > Maybe it would be better to add it just to ConcurrentDistributedMap directly > and not LockableMap for the moment? I was thinking at LockableMap in order to be consistent with already existing interfaces: adding such a method directly on ConcurrentDistributedMap would absolutely work for me, but I don't want to mess your code, so feel free to review the issue with your transparency team if needed and keep me posted. As an alternative solution, I was thinking to write a ContentionManager to simply kill threads contending/waiting-for locks for too much time, so I have another question: is it possible to interrupt a thread waiting on ManagerUtil.beginLock(...)? -- Sergio Bossa Software Passionate and Open Source Enthusiast. URL: http://www.linkedin.com/in/sergiob _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
