jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCR-3395) separate entries used for permission eval from ACEs exposed in JCR
Date Tue, 07 Aug 2012 12:27:08 GMT

     [ https://issues.apache.org/jira/browse/JCR-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

angela resolved JCR-3395.
-------------------------

       Resolution: Fixed
    Fix Version/s: 2.5.2
    
> separate entries used for permission eval from ACEs exposed in JCR
> ------------------------------------------------------------------
>
>                 Key: JCR-3395
>                 URL: https://issues.apache.org/jira/browse/JCR-3395
>             Project: Jackrabbit Content Repository
>          Issue Type: Sub-task
>          Components: jackrabbit-core, security
>            Reporter: Julian Reschke
>             Fix For: 2.5.2
>
>         Attachments: JCR-3395.patch
>
>
> See: https://issues.apache.org/jira/secure/attachment/12533955/JCR-2950_entryseparation.patch
> yet another patch that will allow us to try further improvements later on: the patch
adds complete separation of entries used for permission eval from ACEs exposed on the JCR
API level. consequently i had to rewrite the retrieval of effective policies (that were using
the entry collector as well). in addition i had to remove the EntryCollectorTest#testIsCached
as they were relying on the effective policies actually exposing the entries in the cache.
this is no longer the case for the reason above.
> this patch most probably doesn't add a major performance gain itself, but it really reduces
the entries stored in the cache to the information required for permission-eval omitting all
additional stuff that is used for JCR API compliance. in addition it would allow us try if
it was beneficial to use multiple sessions to collect the entries. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message