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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/05/21 15:51:17 UTC

[jira] [Commented] (OAK-834) Efficient copying of binaries across repositories with the same MK

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

Jukka Zitting commented on OAK-834:
-----------------------------------

In general I see the JCR-3534 solution as an artifact of a poor deployment architecture driven by the limitations of the Jackrabbit architecture. Thus instead of replicating the solution as-is in Oak I'd rather look at making sure that Oak can better handle such deployment needs without needing such workarounds.

That said, it looks like for backwards compatibility and for ease of migration we'll need to include some level of support for existing Jackrabbit DataStores. Perhaps that's a good starting point?
                
> Efficient copying of binaries across repositories with the same MK
> ------------------------------------------------------------------
>
>                 Key: OAK-834
>                 URL: https://issues.apache.org/jira/browse/OAK-834
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mk
>            Reporter: Tommaso Teofili
>
> As a follow up on JCR-3534 discussions and implementation, we should also discuss how to handle a similar scenario in Oak.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira