[
https://issues.apache.org/jira/browse/JCR-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617374#action_12617374
]
Carsten Ziegeler commented on JCR-1672:
---------------------------------------
I'm not sure what the best wording might be, but I think isExternal is "ok" -
for me the opposite of isLocal would be isRemote :)
> Adding Event interface and isLocal()
> ------------------------------------
>
> Key: JCR-1672
> URL: https://issues.apache.org/jira/browse/JCR-1672
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-api, jackrabbit-core
> Affects Versions: 1.4
> Reporter: Carsten Ziegeler
> Fix For: 1.5
>
> Attachments: jackrabbit.patch, localeventlistener.patch
>
>
> when a repository cluster is used, it seems that a common problem many people
> have is to detect if an observation event is send because of changes on the
> local instance or a remote instance of the cluster.
> This is especially important if you want to do post processing of data
> based on observation (the post processing should only be done by one instance
> in the cluster).
> A current solution is to cast the jcr event object to the EventImpl of
> jackrabbit core which is obviously not a nice solution :)
> So what about adding an event interface to jackrabbit api which extends the
> jcr event interface and adds the isLocal() method?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
