Hi, I've been reading through the issues in Jira that are related with additional info: http://jira.terracotta.org/jira/browse/RMP-133 http://jira.terracotta.org/jira/browse/RMP-91 http://jira.terracotta.org/jira/browse/RMP-204
For completeness, these are related, but have no info: http://jira.terracotta.org/jira/browse/CDV-322 http://jira.terracotta.org/jira/browse/DEV-825 From the transparency meeting of yesterday, it seems that these are the tasks that have been discussed before (I wasn't there at that time): * replace CHM ReentrantLocks with ReentrantReadWriteLocks * support partial values like the regular HashMap Issue RPM-133 confirms the ReentrantReadWriteLock plan which is backed up with RPM-91. However, when I look through the code I can see that we have a ReentrantReadWriteLockClassAdapter that is activated in the BootJarTool together with other stuff in the addInstrumentedReentrantReadWriteLock() method. How much of this is supported? does anyone know if this is what issue RPM-91 demands? Also, I would appreciate to hear any additional information about this that might have been discussed during previous meetings, before my time. Should I talk to anyone else besides Antonio about the current HashMap implementation and possible ideas for CHM (Tim maybe?). I'd love to setup a conference call to make it easier for me to get started with what's already there and have a cleared picture of where to go. Thanks! Geert -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
