Web Component Discovery for Unified Client-Server Rendering

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing web application technologies require multiple data structures for client and server-side rendering, leading to inefficient use of computing resources and the need for separate version management and updates.

Innovation Solution

A web application component discovery device that facilitates the use of a single web application component data structure, enabling simultaneous rendering on both client and server sides by providing location information to user and application server devices, thus eliminating the need for duplicate data structures and reducing resource consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple data structures are used for client and server-side rendering, then rendering functionality is maintained, but computing resources are inefficiently used and version management becomes complex

Engineering Contradiction:

Improverendering functionalityVSAvoiddata structure management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the previously separate client-side and server-side data structures into a single unified web application component data structure. This single data structure contains all necessary information for both client-side rendering (via component transfer objects) and server-side rendering (via component bundles), eliminating the need to maintain multiple separate data structures and their versioning schemes.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The unified web application component data structure serves multiple functions simultaneously: it acts as the source for generating both client-side component transfer objects and server-side component bundles. This multi-functional design allows a single data structure to support both rendering scenarios without requiring separate version management systems.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If separate data structures are maintained for client and server sides, then specific rendering requirements are met, but resource consumption increases

Engineering Contradiction:

Improverendering scenario supportVSAvoidcomputing resource consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

By combining the data structures into one unified source, the system eliminates redundant storage and processing. The single web application component data structure is used to generate both client and server rendering artifacts, reducing the total computational resources required for maintaining multiple separate data structures.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

Instead of maintaining separate master data structures, the system creates copies (component transfer objects for client-side, component bundles for server-side) from a single source data structure. This copying approach allows both rendering scenarios to have their required formats while consuming fewer resources than maintaining separate source structures.

Inventive Principle:

Principle #26Copying

3Ease of operation

If duplicate data structures are used, then both rendering scenarios can operate independently, but version synchronization becomes difficult

Engineering Contradiction:

Improveindependent operationVSAvoidversion synchronization time

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The patent merges version management into a single process by using one unified web application component data structure as the sole source of truth. Updates are made to this single structure, and both client and server rendering artifacts are regenerated from the updated source, eliminating the time-consuming process of synchronizing versions across multiple separate data structures.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary generation of both client and server rendering artifacts from the unified data structure during build time. This preliminary action ensures that both rendering scenarios have their required components ready, and any version updates automatically propagate to both scenarios through regeneration from the single source.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12506811B2Systems and methods for facilitating rendering of a web application component by different devices

Publication Date: 2025.12.23 CAPITAL ONE SERVICES LLC

AI summary

A web application component discovery device receives, from an application server device, a first location request associated with a web application component; identifies, using the first location request, a location of the web application component; and sends, to the application server device, first information indicating the location of the web application. This allows the application server device to obtain and render a first copy of the web application component. The web application component discovery device receives, from a user device, a second location request associated with the web application component; identifies, using the second location request, the location of the web application component; and sends, to the user device, second information indicating the location of the web application component. This allows the user device to obtain and render a second copy of the web application component.