Application Gateway for Browser Component Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Browser-based applications face challenges in managing communication between isolated components within a browser environment, requiring architectures that enable separate updates without compromising the stability of the entire application, while also dealing with the limitations of operating within a browser environment.

Innovation Solution

An application gateway is introduced to facilitate controlled communication between application components using dispatching and listening API wrappers, enabling asynchronous and asymmetric communication while maintaining component isolation, allowing for seamless updates and integration of new components without prior coordination.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If application components communicate directly in a browser-based environment, then communication efficiency is improved, but component isolation and stability are compromised

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidcomponent isolation and stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces an application gateway as an intermediary component that mediates all communications between application components. The gateway provides a controlled interface through which components can communicate asynchronously, maintaining isolation while enabling efficient interaction. This mediator approach allows the system to achieve both communication efficiency and component stability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If application components are tightly integrated for seamless operation, then application functionality is improved, but update flexibility and independence are reduced

Engineering Contradiction:
Improveupdate flexibilityVSAvoidapplication functionality
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the application into independent components that communicate through the application gateway. Each component maintains its own isolation and can be updated independently without affecting other components. The gateway maintains the overall application functionality by coordinating these segmented components asynchronously, enabling both update flexibility and functional integrity.

Inventive Principle:
Principle #1Segmentation

3Reliability

If a communication architecture is implemented to maintain component isolation, then stability is improved, but communication complexity increases

Engineering Contradiction:
Improvecomponent isolationVSAvoidcommunication architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The application gateway serves multiple functions: it provides controlled communication interfaces, manages asynchronous messaging, coordinates component interactions, and maintains isolation boundaries. By consolidating these multiple functions into a single universal component, the patent reduces overall system complexity while maintaining component isolation and stability.

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

Data Source

PatentUS9043807B2Application gateway in a browser based environment
Publication Date: 2015.05.26 CHEGG
  • US9043807B2 patent drawing
  • US9043807B2 patent drawing
  • US9043807B2 patent drawing

AI summary

An application gateway enables controlled communication between application components within a browser based environment while maintaining a level of isolation of the individual application components. A dispatching API wrapper and a listening API wrapper are registered for each of a plurality of application components. The registered API wrappers are used to send and receive communications from the associated application components. For example, a first application component can dispatch an action to a second application component via the first application component's dispatching API wrapper. The second application component can receive the action via the second application component's listening API wrapper. As another example, a first application component can dispatch an event that broadcasts a state to other application components via the first application component's dispatching API wrapper. A listening API wrapper of at least one other application component receives the state and may perform other functions dependent on the state.