jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-167) Caching NodeStore implementation
Date Thu, 05 Jul 2012 12:06:33 GMT

    [ https://issues.apache.org/jira/browse/OAK-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407028#comment-13407028

Stefan Guggisberg commented on OAK-167:

IMO we have no choice but buffer transient changes (-> 'transient space') in oak-jcr. otherwise
i don't see how we could efficiently remote the JCR api. buffering the transient changes in
oak-core would mean that every Node.addNode and Node.setProperty would trigger a server round-trip.
that's not an option. see also OAK-162.
> Caching NodeStore implementation
> --------------------------------
>                 Key: OAK-167
>                 URL: https://issues.apache.org/jira/browse/OAK-167
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core
>            Reporter: Jukka Zitting
> For remote MicroKernel implementations and other cases where local caching of content
is needed it would be useful to have a NodeStore implementation that maintains a simple in-memory
or on-disk cache of frequently accessed content. 
> Such a NodeStore implementation could also be used to better isolate the current caching
logic behind uncommitted changes.

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


View raw message