[
https://issues.apache.org/jira/browse/OAK-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663054#comment-13663054
]
Thomas Mueller commented on OAK-834:
------------------------------------
I see your point. But I still see a value in supporting distinct
(non-clustered; possibly peer-to-peer) repositories with a shared data store,
even with Oak.
> JCR features like Node.update()
I'm sorry, what is Node.update()?
> 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
