[
https://issues.apache.org/jira/browse/OAK-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410514#comment-13410514
]
Michael Dürig commented on OAK-156:
-----------------------------------
In revision 1359763 I added a refresh call each time before the observation
events are calculated. Since the refresh call happens from another thread, I
had to synchronize access to the {{Root}} instance in {{SessionDelegate}}.
Currently this is done through explicit synchronisation on the {{Root}}
instance's object monitor. The result of which is that concurrent read access
within the same session will also be synchronised to some degree. If this turns
out to lead to contentions, we could change the synchronisation mechanism to
use some sort of a read write lock.
> Observation events need Session.refresh
> ---------------------------------------
>
> Key: OAK-156
> URL: https://issues.apache.org/jira/browse/OAK-156
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Reporter: Michael Dürig
> Fix For: 0.4
>
>
> The observation design from OAK-144 does not deliver events from revisions
> which are ahead of the revision on which the current session is based. A call
> to session.refresh or session.save will cause such events to be dispatched.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
