Composite Event Sequence for Application Performance Tracing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web and mobile applications face challenges in consistently measuring performance metrics across different user actions, as these actions generate varying event sequences depending on the input device used, leading to inconsistent event handling and analysis.
Innovation Solution
The implementation of dummy action handlers for non-significant event listeners ensures that all user actions result in a uniform composite event sequence, allowing for the measurement and logging of performance metrics across different event types, thereby standardizing the analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different event listeners are used for different input devices, then device-specific functionality is achieved, but performance metric measurement becomes inconsistent
Solution Approach 1:
The patent introduces composite event sequences as an intermediary layer between raw device-specific events and performance measurement. This mediator standardizes different input device events (mouse, touch, keyboard) into a unified event structure, allowing consistent performance metric collection while preserving device-specific functionality through the mapping process
2Adaptability or versatility
If multiple event handlers are added to handle different events, then comprehensive event coverage is achieved, but system complexity increases
Solution Approach 1:
The patent merges multiple device-specific event handlers into a unified composite event sequence handler. By combining mouse events, touch events, and keyboard events into a single standardized event structure, the system achieves comprehensive event coverage while reducing the number of separate handlers needed, thus lowering overall system complexity
Solution Approach 2:
The composite event sequence serves as a universal handler that processes multiple types of input device events through a single mechanism. This multi-functional approach allows the same event processing logic to handle different input types, reducing the need for device-specific code paths and simplifying the overall system architecture
Data Source
AI summary
Examples disclosed herein relate to a system for generating an element identifier comprising an action engine to identify at least one event listener associated with a significant event in an application, receive an action associated with an element of the application, generate a composite event sequence comprising a plurality of event listeners associated with the action, and determine whether the composite event sequence is associated with the at least one significant event. The system may further comprise a metric engine to measure a performance metric associated with the received action and create a log record according to the composite event sequence comprising the performance metric.