Infinispan Cache Listeners: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
=Overview= | =Overview= | ||
Infinispan offers a listener API that can be used by clients to register listeners for cache and cache manager events. It is an annotation-driver API. An event triggers a ''notification'' which is dispatched to listeners. | |||
=Code= | =Code= | ||
| Line 16: | Line 18: | ||
c.addClientListener(cl); | c.addClientListener(cl); | ||
</pre> | </pre> | ||
=Difference between Listeners and Client Listeners= | |||
<font color=red>TODO</font> | |||
=Client Listener Organizatorium= | |||
<font color=red> | |||
When a Hot Rod client registers a client listener, it does so in a single node in a cluster. See http://infinispan.org/docs/8.0.x/user_guide/user_guide.html#client_event_listener_failure_handling | |||
<font> | |||
Latest revision as of 02:53, 28 October 2016
External
Internal
Overview
Infinispan offers a listener API that can be used by clients to register listeners for cache and cache manager events. It is an annotation-driver API. An event triggers a notification which is dispatched to listeners.
Code
RemoteCache<String,Integer> c = ...; cl = new CacheListenerImpl(); c.addClientListener(cl);
Difference between Listeners and Client Listeners
TODO
Client Listener Organizatorium
When a Hot Rod client registers a client listener, it does so in a single node in a cluster. See http://infinispan.org/docs/8.0.x/user_guide/user_guide.html#client_event_listener_failure_handling