[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-961) Optimistic locking to support more sophisticated merging of child maps

[Manik Surtani (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCACHE-961?page=comments#action_12355328 ] 
            
Manik Surtani commented on JBCACHE-961:
---------------------------------------

Fixed.  Implements 2 simple sets of children added and children removed in the workspace node.  This is used to apply changes to the underlying cache.  See WorkspaceNode.isDirty() and WorkspaceNode.isChildrenModified() javadocs for details.

> 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.GA, 2.0.0.BETA2
>
>
> 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