[infinispan-issues] [JBoss JIRA] (ISPN-3355) Add support for clustered listeners

[Desmond Kirrane (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12936722#comment-12936722 ] 

Desmond Kirrane commented on ISPN-3355:
---------------------------------------

Few comments on the ClusterListeners:
- Can the listener be made durable i.e. if the primary dies then the listener will be registered on the backup
- Can the listener use a query api e.g. notify me of any Books having "title" like "%engine%"
- Can the listener add the option to remove or modify the entry/entires its query matches.

                
> Add support for clustered listeners
> -----------------------------------
>
>                 Key: ISPN-3355
>                 URL: https://issues.jboss.org/browse/ISPN-3355
>             Project: Infinispan
>          Issue Type: Feature Request
>            Reporter: Mircea Markus
>            Assignee: William Burns
>
> As opposed to the current listener approach in Infinispan ( a listener instance is invoked on the data owners ), this JIRA is about adding support for a cluster listener: the same listener instance that is notified disregarding of data ownership ( RPC calls involved). 
> Due to the fact that the listener notification might involve an RPC, it is nice to be able to specify filters on these listeners.
> The clustered listener support opens the way for some interesting architectures:
> * persistent/continuous queries: the query is transformed in a filter. On each notification, the listener (stateful) updates the query state
> * simplistic CEP can be built on top of the persistent query described above
> * remote/hotrod notifications might be based on clustered listeners as well.

--
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