Skip to main content

Short note: JINI distributed event spec

Short answer

Jini distributed events enable notification across JVMs using RemoteEventListener. Generators register listeners, returning an EventRegistration with a lease. Events carry sequence numbers for ordering, and third-party agents can filter or store them.

Write a short note on JINI Distributed Event Specification.

JINI Distributed Event Specification defines how objects in a Java/Jini network are notified when something happens in another object, as an extension of the Java event model across address spaces.

  • Event generator: the object where events occur. It has a register method for interested parties.
  • RemoteEventListener: interface implemented by a subscriber, with a method notify(RemoteEvent).
  • RemoteEvent: carries the event identifier, the source, a sequence number (to detect lost or out of order events) and a handback object given by the listener at registration.
  • EventRegistration: returned on registering; it includes a lease.
  • Leases: registration is for a limited time and must be renewed, so dead listeners are cleaned up.
  • Third-party agents: a mailbox, filter or store can sit between generator and listener to forward, filter or store events.

Notifications are delivered by RMI. Delivery is neither guaranteed nor ordered, so listeners use the sequence number to detect missing or out-of-order events.

✓ Answer checked by Claude Opus 5.5 (high effort)

Related questions

All Distributed System chapter 2 questions →