You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2012/07/05 10:45:34 UTC

[jira] [Comment Edited] (OAK-167) Caching NodeStore implementation

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

Stefan Guggisberg edited comment on OAK-167 at 7/5/12 8:44 AM:
---------------------------------------------------------------

> Such a NodeStore implementation could also be used to better isolate the current caching logic behind uncommitted changes.

wouldn't that ideally be the transient space, i.e. oak-jcr?
                
      was (Author: stefan@jira):
    > Such a NodeStore implementation could also be used to better isolate the current caching logic behind uncommitted changes.

wouldn't that ideally the transient space, i.e. oak-jcr?
                  
> 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