[ https://issues.apache.org/jira/browse/OAK-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489393#comment-13489393 ]
Michael Dürig commented on OAK-418: ----------------------------------- In revision 1404945 I added a revision counter in {{SessionDelegate}} and {{ItemDelegate}}. Initially an item will get the same revision as the session which created it. When a session does a save or refresh its revision will increment. When an item is accessed, it will check whether its revision matches that of the session. If not, a refresh or save must have happened in the meanwhile and the item needs to re-resolve its underlying state. Until now, that re-resolving was done on every access of an item. The revision tracking reduces the number of re-resolving by a couple of orders of magnitude. > Reduce/avoid re-resolving the underlying tree instances on every access in > Item/Property/NodeDelegate > ------------------------------------------------------------------------------------------------------ > > Key: OAK-418 > URL: https://issues.apache.org/jira/browse/OAK-418 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: jcr > Reporter: Michael Dürig > > With the changes in behaviour of the move operation introduced with OAK-391 > this re-resolving should be mostly obsolete. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira