Optimistic locking to support more sophisticated merging of child maps ---------------------------------------------------------------------- Key: JBCACHE-961 URL: http://jira.jboss.com/jira/browse/JBCACHE-961 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.1.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.BETA2, 2.0.0.GA At the moment at commit time parent nodes in a workspace have their child maps used to overwrite the underlying data nodes. As such, version increments are necessary on the parents, very bad for concurrency. A more sophisticated merging mechanism is needed here, perhaps along the lines of: 1) Children added placed in an addedChildren map 2) Children removed placed in a childrenRemoved map at commit time, use these 2 maps to look at what exists in the underlying node and merge in accordingly. Related to JBCACHE-955 and JBCACHE-956. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira