# US 2008/0307437 A1 · Method and System for Time Bounding Notification Delivery in an Event Driven System

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0307437 A1
- Document ID: US20080307437A1
- Status: Published application
- Kind: A1
- Application number: 12/180,981
- Filed: 2008-07-28
- Published: 2008-12-11
- Earliest claimed: 2004-12-02
- Assignees: International Business Machines Corporation
- Inventors: Ward K. Harold; Shawn William Lauzon
- Web page: https://patentgrep.com/patent/US20080307437A1

## CPC

- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 9/485: {Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present invention is directed to a method and system for preventing unnecessary delays during notification delivery process in an event driven system. The unnecessary delays may be caused by waiting for event completion acknowledgments for an unbounded time. Notifications (event handle requests) may be dispatched to all interested parties in parallel. Then, handling acknowledgments from the interested parties may be gathered after a specific delay. Termination requests may be sent to non-responding parities in order to prevent indefinite waiting or an advertent notification cycle. Alternatively, non-responding parties may be removed from a list of listeners which have been registered as interesting parties for a software component in the event driven system.

## Claims

### Claim at position 1

1-19. (canceled)

### Claim 20

An event driven system comprising:
a computer network;
a notification broadcaster for sending handle requests for an event;
a plurality of listeners communicatively coupled to the notification broadcaster, each one of the plurality of listeners configured to receive the handle requests and send an acknowledgment after completing an action in accordance with the handle requests,
wherein the notification broadcaster proceeds to a next operation after a time bound and sends a termination request to any of the plurality of listeners which have not sent acknowledgements in the time bound to prevent delay from waiting for acknowledgments, wherein each of the plurality of listeners is configured to cancel completing an action in accordance with the handle requests in response to receipt of a termination request, and
wherein each of the plurality of listeners is registered as an interested party in a software component in the event driven system and the notification broadcaster cancels the registration as an interested party of any of the plurality of listeners which have not sent acknowledgments in the time bound to prevent future handle requests from being sent to any of the plurality of listeners which have not sent acknowledgments in the time bound.

### Claim 21 (depends on 20)

The event driven system as described in claim 20, further comprising a notification dispatcher coupled to the notification broadcaster and the plurality of listeners,
wherein the notification dispatcher relays handle requests and acknowledgements from/to the broadcaster and the plurality of listeners.

### Claim 22 (depends on 21)

The event driven system as described in claim 21, wherein the notification dispatcher sends an acknowledgement to the broadcaster after the notification dispatcher determines that there is no outstanding event handle request.

### Claim 23 (depends on 22)

The event driven system as described in claim 22, wherein the outstanding event handle request is terminated after the time bound.

### Claim 24 (depends on 20)

The event driven system as described in claim 20, wherein the notification broadcaster sends the handling requests when it detects a triggering event.

### Claim 25

A system for time bound notification delivery, comprising:
means for registering all interested parties of a software component to a listener list, wherein the listener list comprises a plurality of listeners;
means for detecting any triggering event;
means for sending an event handle request, in parallel, to the listeners of the listener list upon detection of the triggering event, wherein the listeners are configured to perform an action related to the event handling request in response to receiving the event handling request;
means for receiving an acknowledgement from a listener of the listener list, wherein each acknowledgment is a completion acknowledgment from a listener of the listener list when action related to the event handling request is accomplished;
means for sending a termination request to a non-responding listener when the non-responding listener has not sent the acknowledgment in a time bound to prevent delay from waiting for the acknowledgment, wherein the non-responding listener is configured to cancel performance of the event handling request in response to receiving the termination request; and
means for removing a non-responding listener from the listener list when the non-responding listener has not sent the acknowledgment in a time bound to prevent future event handling requests from being sent to the non-responding listener.

### Claim 26 (depends on 25)

The system as described in claim 25, further comprising:
means for relaying the event handle request;
means for sending an acknowledgement after determining that outstanding event handle requests have been handled in the time bound.
