ABAP Event Dispatcher for Modular Application Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current eventing mechanisms in programming languages, such as ABAP, require anticipating all event types and lack control over event consumption order, especially in modular applications, which is not feasible with remote function calls.

Innovation Solution

A new ABAP statement allows monitoring of event channels until a logical expression is satisfied, with an optional timeout, enabling a generic event handler without remote function calls, allowing applications to control event consumption and processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If remote function calls are used for event handling, then event consumption can be controlled, but the system complexity increases and modular applications cannot express their interest in event consumption

Engineering Contradiction:
Improveevent consumption controlVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an event dispatcher as an intermediary component that sits between event sources and event handlers. This dispatcher manages the event queue, routes events to appropriate handlers based on conditions, and coordinates communication between modular components. By using this intermediary, the system achieves event consumption control without the complexity of remote function calls, and modular applications can express their interest in events through registered handlers with associated conditions.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If dedicated function handlers are assigned to each event type, then event handling is straightforward, but the programming language creator must anticipate all event types which is not feasible

Engineering Contradiction:
Improveevent handling implementationVSAvoidevent type coverage
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal event dispatcher that can handle multiple event types through a single mechanism. Instead of requiring dedicated functions for each event type, the dispatcher uses a standardized interface where event handlers register their interest in specific event types through conditions. This universal approach allows the system to handle both anticipated and unforeseen event types dynamically, achieving adaptability while maintaining ease of implementation through the standardized dispatcher interface.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The event handling system is made dynamic through condition-based event registration. Handlers can specify conditions under which they want to receive events, and the dispatcher dynamically routes events based on these conditions at runtime. This dynamic approach allows the system to adapt to new event types without requiring predetermined function assignments, as handlers can register for events dynamically based on their needs.

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If conditions are specified for event receipt, then event consumption can be controlled, but modular applications cannot express their interest in event consumption

Engineering Contradiction:
Improveevent receipt controlVSAvoidmodular application flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the event handling system into independent modular components: event sources, event queue, event dispatcher, and event handlers. Each modular application can register as an event handler with specific conditions, expressing its interest in event consumption without affecting other modules. This segmentation allows conditions to be specified for event receipt while maintaining modular application flexibility, as each module operates independently but coordinates through the standardized dispatcher interface.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9043815B2Programming language conditional event dispatcher
Publication Date: 2015.05.26 SAP SE
  • US9043815B2 patent drawing
  • US9043815B2 patent drawing
  • US9043815B2 patent drawing

AI summary

Methods and systems of monitoring events occurring in a computer system are provided. An event monitoring instruction including a condition is parsed, the event monitoring instruction expressed using syntax defined in source code, the parsing resulting in an event channel to monitor and the condition. Then execution of an application is paused. The event channel is monitored until an event occurs on the event channel. Then an event handler for the event is run in response to the event occurring on the event channel. The condition is evaluated to determine whether the condition is satisfied. Execution of the application is resumed in response to the condition being satisfied.