[
https://issues.apache.org/jira/browse/OAK-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632881#comment-13632881
]
Michael Dürig edited comment on OAK-775 at 4/16/13 3:53 PM:
------------------------------------------------------------
At revision 1468477 I committed a first version of a "more backward compatible"
version of observation as described. The implementation currently lives in its
own package {{observation2}} and is disabled by default. It can be globally
enabled by specifying {{-DOAK-775=true}} on the command line. In addition to
the test passing with the existing implementation this implementation also
passes the user id and user data related TCK tests ({{EventTest#testGetUserId,
GetUserDataTest#testSave, GetUserDataTest#testWorkspaceOperation}}).
To be done:
* Unify the implementations in {{observation}} and {{observation2}} to reduce
code duplications
* Allow clients to select the implementation when registering an event listener
* Filter events by session access restrictions
* Clarify security implications of the event queue
* Currently the observation manager needs write access to
{{/jcr:system/rep:observation/listeners}}.
* Persist events across restarts. Currently the queue is purged after a
restart. See FIXME in {{ObservationManager2.clearEventQueueOnRestart}}
* Clarify impact of clustering on repository internal event queue
was (Author: mduerig):
At revision 1468434 I committed a first version of a "more backward
compatible" version of observation as described. The implementation currently
lives in its own package {{observation2}} and is disabled by default. It can be
globally enabled by specifying {{-DOAK-775=true}} on the command line. In
addition to the test passing with the existing implementation this
implementation also passes the user id and user data related TCK tests
({{EventTest#testGetUserId, GetUserDataTest#testSave,
GetUserDataTest#testWorkspaceOperation}}).
To be done:
* Unify the implementations in {{observation}} and {{observation2}} to reduce
code duplications
* Allow clients to select the implementation when registering an event listener
* Filter events by session access restrictions
* Clarify security implications of the event queue
> 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.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
