[
https://issues.apache.org/jira/browse/OAK-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632884#comment-13632884
]
Jukka Zitting commented on OAK-709:
-----------------------------------
In revision 1468435 I addressed the equals() FIXME with a really simple
implementation of the above "security context" concept.
Instead of a more fine-grained context, I'm simply using the entire repository
revision (as encapsulated in the raw root node state) and the path of a node as
the security context. If both are equal for two SecureNodeState instances,
they're guaranteed to be equal also as defined for NodeState.equals().
I left a TODO for further optimization, but this basic optimization already
achieves the same effect as the previous hacky workaround, whose remnants I
removed in revision 1468441.
> Consider moving permission evaluation to the node state level
> -------------------------------------------------------------
>
> Key: OAK-709
> URL: https://issues.apache.org/jira/browse/OAK-709
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core
> Reporter: angela
> Attachments:
> 0001-OAK-709-Consider-moving-permission-evaluation-to-the.patch,
> 0001-OAK-709-Consider-moving-permission-evaluation-to-the.patch,
> 0001-OAK-709-Consider-moving-permission-evaluation-to-the.patch,
> 0001-OAK-709-Consider-moving-permission-evaluation-to-the.patch,
> OAK-709_2.patch, OAK-709_3.patch, OAK-709_4.patch, OAK-709-equals_hack.patch,
> OAK-709.patch, OAK-709-shadowing_nodes.patch, SecureNodeState.java
>
>
--
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
