Asynchronous Browser Workload Execution With Real-Time UI Feedback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web-based workload management systems experience substantial lag times due to users waiting for workload completion, and existing background sessions lack real-time feedback mechanisms, making it difficult to monitor workload status and respond to errors.
Innovation Solution
The system delegates workload execution to background sessions while providing real-time monitoring through a feedback mechanism within the user interface, allowing asynchronous processing and concurrent workload execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If workload execution is performed in the main session, then real-time feedback can be provided to the client application, but the client application experiences substantial lag times and cannot execute other processing tasks during workload execution
Solution Approach 1:
The patent segments the workload execution process by creating a separate background session that operates independently from the main session. The main session handles client communication and feedback, while the background session executes the actual workload. This segmentation allows the client application to remain responsive and execute other tasks without waiting for workload completion, while still receiving real-time status updates through the main session's event handlers.
2Productivity
If workload execution is delegated to background sessions, then the client application can continue working without delay, but the user is unable to receive feedback through the client application pertaining to workload status
Solution Approach 1:
The patent implements a feedback mechanism where event handlers are configured in both the main session and background session. When the background session generates workload status events during execution, the event handlers capture these events and transmit status update instructions back to the client application. This feedback loop ensures that users receive real-time workload status information through the client application's user interface, maintaining information flow despite asynchronous execution.
Solution Approach 2:
The patent uses event handlers as intermediaries to bridge the communication gap between the background session and the client application. The event handlers in the main session act as mediators that receive workload status events from the background session and translate them into status update instructions that the client application can process and display. This intermediary mechanism enables indirect communication while maintaining the benefits of asynchronous background execution.
3Reliability
If synchronous workload processing is used, then complete control and monitoring is maintained, but user interface responsiveness deteriorates due to waiting for workload completion
Solution Approach 1:
The patent applies dynamics by making the session structure flexible and adaptive. The system dynamically creates background sessions for workload execution while maintaining dynamic event handler configurations that respond to workload status changes. The main session can dynamically adjust its event handling based on the state of background sessions, allowing the system to maintain reliable control over workload execution while adapting to maintain user interface responsiveness throughout the asynchronous processing lifecycle.
Data Source
AI summary
A workload management system includes a workload management tool configured to generate a workload context associated with a workload generated based on interactions of a user with workload initiation controls presented within a user interface (UI) of a client application. The workload context includes instructions for transmitting the workload context from a main browser session to a first background browser session; executing the workload within the first background session; and for configuring a first event handler within the main session to wait for a first event generated within the first background session in association with execution of the workload and, in response to receipt of the first event, transmit the client application an instruction to present workload status information in the user interface.