[
https://issues.apache.org/jira/browse/OAK-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621894#comment-13621894
]
angela commented on OAK-709:
----------------------------
ok... so, it will include major refactoring :-)
i suggest to create
- SecureNodeStore (in a first step for each content session) that holds the
permissionprovider
- SecureNodeState internally wrap the NodeState in ImmutableTree such as the
PermissionValidator does
and which keeps the ReadStatus that is currently located on the TreeImpl.
that one reveals
if child nodes and properties need extra access evaluation.
we may still make this part of the API later on but i first would like to have
a prove of concept
showing that it works as this (or alternatively OAK-704) is currently blocking
any further
work on the permission evaluation.
i will try to come up with a patch that we could discuss later in the oakathon
next week.
> 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,
> 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
