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

Posted to dev@jackrabbit.apache.org by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org> on 2012/03/06 19:06:59 UTC

[jira] [Updated] (OAK-3) Internal tree model

     [ https://issues.apache.org/jira/browse/OAK-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated OAK-3:
----------------------------

    Attachment: OAK-3.1.patch

I added the discussed interfaces to .oak.tree (perhaps .oak.model would be better?).

I also drafted the attached a simple patch as the first attempt to integrate the abstraction to the existing MK code. The idea here is to start decoupling the MicroKernelImpl and Repository classes from the underlying code in .mk.store and .mk.model.
                
> Internal tree model
> -------------------
>
>                 Key: OAK-3
>                 URL: https://issues.apache.org/jira/browse/OAK-3
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>         Attachments: OAK-3.1.patch
>
>
> As [discussed|http://markmail.org/message/qdvl5zz5cpkoxz3j] recently on dev@, I'd like to introduce an internal tree model for abstracting read access to the underlying storage implementation. We seem to have reached a rough consensus on the interfaces, so it's time to move them to svn.

--
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