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

[William Burns (JIRA)]

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

William Burns commented on ISPN-3355:
-------------------------------------

Desmond,

# Currently there is no plan for this in embedded mode.  There were talks about adding this in a future iteration for embedded.  Hotrod with remote listeners is planned to register a new listener on a new node.  That is covered in ISPN-374
# The user can provide a Filter that can be used for given keys.  The final plan is to have a Filter that can use the new Query DSL to filter these in ways like you mentioned.  However core itself will not support the query filtering.  This will require an additional module that is actively being worked on (don't know the JIRA)
# There is no thought of allowing this at this point.  This doesn't preclude the ability for the user to trigger a write update in response to the event occurring though.  However you should not raise such an event in the listener as this would cause a deadlock for synchronous events as it is fired when the lock is still acquired.
                
> 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