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-2703) UserManagement: Add Membership Cache
Date Wed, 11 Aug 2010 10:30:24 GMT

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

angela resolved JCR-2703.
-------------------------

    Resolution: Fixed

> UserManagement: Add Membership Cache
> ------------------------------------
>
>                 Key: JCR-2703
>                 URL: https://issues.apache.org/jira/browse/JCR-2703
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, security
>    Affects Versions: 2.0.0, 2.1.0
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.2.0
>
>
> due to weakreference nature of the group members, retrieving the groups a given authorizable
is member is expensive as the corresponding
> API call (Node#getWeakReferences) executes a query [fallback if search is disabled: traversing
the complete group tree, which isn't for free either].
> i would therefore suggest to add a cache (authorizable nodeId -> group nodeids) that
is gets cleared upon any modification to group membership or
> group removal and doesn't need any extra observation. this cache may potentially obsolete
the principal-based cache in DefaultPrincipalProvider... 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message