[ 
https://issues.apache.org/jira/browse/JCR-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899545#action_12899545
 ] 

Joel Feenstra commented on JCR-2573:
------------------------------------

I am seeing a sporadic failure to read a file using webdav with Jackrabbit 
2.1.0. If I share a nt:folder and apply permissions to it to make it read-only 
for some users, sometimes I am unable to read the properties of an nt:file in 
that folder. I tried our code against Jackrabbit 2.2-SNAPSHOT and it worked 
fine. I tried to find out what change fixes the bug, and it appears to be 
r950440. Are there plans to merge this into the 2.1 branch (I just saw it was 
merged to 2.0).

> Performance of AC Evaluation
> ----------------------------
>
>                 Key: JCR-2573
>                 URL: https://issues.apache.org/jira/browse/JCR-2573
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 2.0.0
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.2.0
>
>         Attachments: acl.zip
>
>
> 1. Performance in access control evaluation
> =====================================================================
>  - main focus on
>    > read performance
>    > resource-based access control in .a.j.c/s/authorization/acl/*
>  - comparison admin vs. anonymous with full permissions
>  - comparision between shortcut and ACL-evaluation.
>  - comparison JR 1.4 vs JR 2.0 [actually i will compare Day's CRX as it 
> already provided
>    some custom AC stuff with JR 1.4]
> 2. Potential Problems
> =====================================================================
>    I would expect the most significant problems to be found in
> a) ACLProvider#retrieveResultEntries: calculating effective ACEs
>      for each session separately.
> b) AclPermission:
>      Each instance registering an event listener in order to
>      keep the result cache up to date
> c) AclPermission:
>      Resolution form Path to Item or to nearest existing Item 

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

Reply via email to