[
https://issues.apache.org/jira/browse/JCR-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485513#comment-14485513
]
Felix Meschberger commented on JCR-3870:
----------------------------------------
bq. there are many other places, where sling is optimized around how the JCR
implementation behaves
Really ? Off the top of my head I know of the Oak Observer (falling back to
regular JCR Observation is not available). Others ?
Indeed, at one point in early time, Sling had JCR Session pooling until
Jackrabbit Repository.login became drammatically faster than pooled session
cleanup. At which time we happily removed Session pooling from Sling.
> Export SessionImpl#getItemOrNull in JackrabbitSession
> -----------------------------------------------------
>
> Key: JCR-3870
> URL: https://issues.apache.org/jira/browse/JCR-3870
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-api
> Affects Versions: 2.10
> Reporter: Joel Richard
> Priority: Critical
> Labels: performance
>
> getItemOrNull should be exported in JackrabbitSession. This would allow to
> combine itemExists and getItem in Sling which would reduce the rendering time
> by 8%.
> See the following mail thread for more information:
> http://mail-archives.apache.org/mod_mbox/jackrabbit-oak-dev/201504.mbox/%3CD1495A09.3B670%25anchela%40adobe.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
