You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/02/16 09:43:11 UTC

[jira] [Commented] (OAK-2520) Expose checkpoints in the ContentSession interface

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

Michael Dürig commented on OAK-2520:
------------------------------------

Apart from my concerns on the list [1] I think creating a {{MutableRoot}} from a checkpoint is risky. I'm not sure whether this will perform or even work properly on all backends. Before going forward with this we should have much better testing in place (including performance).

Furthermore conceptually checkpoints do not belong to the {{ContentSessions}} but to the {{ContentRepository}} as a checkpoint always covers the whole repository and a content sessions only a single workspace. 


[1] http://markmail.org/message/5s3b4zoycpubusee

> Expose checkpoints in the ContentSession interface
> --------------------------------------------------
>
>                 Key: OAK-2520
>                 URL: https://issues.apache.org/jira/browse/OAK-2520
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Francesco Mari
>            Priority: Minor
>         Attachments: OAK-2520-1.patch
>
>
> Checkpoints could be an acceptable solution to implement the concept of "revision" described in the remote API linked from OAK-2502.
> For clients of Oak to use checkpoints, those should be exposed from the {{ContentSession}} API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)