jackrabbit-oak-dev mailing list archives

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

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

Jukka Zitting commented on OAK-167:
-----------------------------------

bq. wouldn't that ideally be the transient space, i.e. oak-jcr?

We in any case need some way to represent uncommitted content in oak-core, as otherwise there's
no way to do things like node type or access control validation before a commit. Instead of
coming up with another data structure for that, it's better to use the one we already have
in the NodeStore/NodeState abstraction. Ideally a caching layer wouldn't even be needed for
this, but that would require more support from the MicroKernel.

                
> 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

        

Mime
View raw message