[
https://issues.apache.org/jira/browse/OAK-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632714#comment-13632714
]
Jukka Zitting commented on OAK-709:
-----------------------------------
An update on the SecureNodeState.equals() case: When running the troublesome
LargeMoveTestIT test case without the current equals() hack, 99.9% of the
equality checks return true. And even more of them match the result of
comparing the underlying raw node states. Unfortunately there's no easy way to
tell if the security contexts of the two states (i.e. all the bits that go into
the ReadStatus calculations) are equal. If such a check was possible, we could
use it to infer equality in the common case when the raw underlying states are
equal and the security contexts of both SecureNodeStates are equal.
So, I'm currently looking at how we could come up with such a "security
context" that encapsulates all the information needed to decide on whether an
item is readable or not. Angela, I'll probably be needing your input on this.
> 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
