Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Distributed event handling mechanism for Java

Tags:

People also ask

What are the event handling mechanisms?

Event Handling is the mechanism that controls the event and decides what should happen if an event occurs. This mechanism have the code which is known as event handler that is executed when an event occurs. Java Uses the Delegation Event Model to handle the events.

What are the main objectives of Jini distributed event specifications?

To show the information needed in any method that allows registration of interest in the occurrence of a kind of event in an object. To provide an example of an interface that allows the registration of interest in such events. To specify an interface that can be used to send a notification of the occurrence of the ...

What is a event handler in Java?

The EventHandler class provides support for dynamically generating event listeners whose methods execute a simple statement involving an incoming event object and a target object.

What is a listener in constant to event handling?

Explanation: A listener is a object that is notified when an event occurs. It has two major requirements first, it must have been registered with one or more sources to receive notification about specific event types, and secondly it must implement methods to receive and process these notifications.


I'm looking for a reasonably fast event handling mechanism in Java to generate and handle events across different JVMs running on different hosts.

For event handling across multiple threads in a single JVM, I found some good candidates like Jetlang. But in my search for a distributed equivalent , I couldn't find anything that was lightweight enough to offer good performance.

Does anyone know of any implementations that fit the bill?

Edit: Putting numbers to indicate performance is a bit difficult. But for example, if you implement a heartbeating mechanism using events and the heartbeat interval is 5 seconds, the heartbeat receiver should receive a sent heartbeat within say a second or two.

Generally, a lightweight implementation gives good performance. A event handling mechanism involving a web server or any kind of centralized hub requiring powerful hardware (definitely not lightweight) to give good performance is not what I'm looking for.