[
https://issues.apache.org/jira/browse/OAK-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640567#comment-13640567
]
Michael Dürig commented on OAK-775:
-----------------------------------
bq. An alternative, hybrid solution that would partially solve the problem...
IIUC we would then have two different type of observation events: internal and
external. The former would provide the user data while the latter would not.
Generating the internal events is easy as you mention: just hook the generation
process into the place where the branch is merged on save. What is not clear to
me is how we stop the internal events from reappearing as external events.
> Implement backward compatible observation
> -----------------------------------------
>
> Key: OAK-775
> URL: https://issues.apache.org/jira/browse/OAK-775
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, jcr
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Attachments: OAK-775-isExternal.patch, OAK-775.patch
>
>
> As [discussed | http://markmail.org/message/6bqycmx6vbq7m25c] we might want
> look into implementing an alternative approach to observation, which trades
> some scalability for improved backward compatibility.
--
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
