[
https://issues.apache.org/jira/browse/JCR-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485498#comment-14485498
]
Tobias Bocanegra commented on JCR-3870:
---------------------------------------
sure...but if this results in 8% performance improvement.... there are many
other places, where sling is optimized around how the JCR implementation
behaves. In Jackrabbit 2.x the item-existance was cached, iirc, so the
itemExits() -> getItem() was fast.
> 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)
