Web Event Framework Plugin Server Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional user environment and policy control mechanisms in computer systems are limited to handling application and system level events and policies, failing to effectively manage web browser-related events and policies such as webpage loading, URL clicks, and tab changes within web browsers.
Innovation Solution
A web event framework that includes a framework plugin embedded in the web browser and a framework server outside the browser, which receives events, generates framework events, determines actions based on policies, and executes these actions, enhancing control over web browser activities and extending policy management to web browser events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional user environment and policy control mechanisms are used, then system simplicity is maintained, but web browser event handling capability is insufficient
Solution Approach 1:
The system is divided into distinct components: a framework plugin embedded in the web browser that captures web events, and a framework server that processes these events and determines actions based on policies. This segmentation allows web browser event handling to be added without complicating the entire system, as each component has a specific, isolated function.
Solution Approach 2:
The framework plugin acts as an intermediary between the web browser and the framework server. It captures web events from the browser, converts them into framework events, and forwards them to the server. This intermediary layer enables web browser event handling without requiring direct integration between the browser and policy control mechanisms, thus maintaining system simplicity while enhancing capability.
2Adaptability or versatility
If policy control is extended to web browser events, then policy management comprehensiveness is improved, but framework maintainability may deteriorate
Solution Approach 1:
The framework server is designed with universal functionality to handle multiple types of events (web browser events, application events, system events) through a common event processing mechanism. This multi-functionality allows comprehensive policy management across different event sources without requiring separate maintenance procedures for each event type, thus improving maintainability while enhancing comprehensiveness.
Solution Approach 2:
The system uses configurable policy parameters that can be modified to extend policy management to web browser events without changing the underlying framework structure. By changing policy parameters rather than framework code, the system achieves comprehensive policy management while maintaining ease of maintenance through non-intrusive configurations.
3Speed
If framework actions are executed by the plugin, then response speed is improved, but system reliability may worsen
Solution Approach 1:
The framework plugin pre-processes web events by converting them into standardized framework events before forwarding to the server. This preliminary action prepares the data in advance, enabling faster server processing and action execution. The pre-conversion reduces the complexity of real-time processing, thereby improving response speed while maintaining reliability through systematic event handling.
Solution Approach 2:
The system implements a feedback mechanism where the framework server determines actions based on received events and policies, then returns these actions to the plugin for execution. The plugin executes actions locally in the browser context, providing immediate feedback. This feedback loop ensures that actions are both fast (executed locally) and reliable (guided by centralized policy decisions from the server).
Data Source
AI summary
Systems and methods are described for a web event framework. A computerized method includes receiving at a framework plugin an event from a web browser, wherein the framework plugin is coupled to the web browser, generating, by the framework plugin, a framework event based on the event, forwarding the framework event to a framework server coupled to the framework plugin, receiving at the framework server the framework event from the framework plugin, determining, at the framework server, a framework action based on the framework event and a framework policy, forwarding the framework action to the framework plugin, and executing the framework action by the framework plugin.