[
https://issues.apache.org/jira/browse/OAK-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631676#comment-13631676
]
Thomas Mueller commented on OAK-775:
------------------------------------
As an alternative to persisting the events, would it be possible to keep the
events in memory, and deliver them after a change was committed?
I understand there would be limitations: only local events could be supported.
And the system could run out of memory, for slow observation listeners or huge
transactions (the same as for Jackrabbit 2.x). But events wouldn't have to be
persisted.
> 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
> Attachments: 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
