Partial-Render Webpage System for Consistent Builds

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

E-commerce websites face challenges in developing scalable and consistent webpage systems to handle high traffic and rapid growth of product listings, requiring improved server systems that support efficient webpage rendering and deployment.

Innovation Solution

A server computer system that initiates a partial-render operation by executing application code to identify object data, making service calls to a data library, and transmitting necessary code and data to client devices for webpage display, allowing for flexible rendering modes and efficient performance optimization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If traditional full rendering is used to ensure consistent webpage builds, then manufacturing precision is improved, but productivity deteriorates due to high server load and slow page generation

Engineering Contradiction:
Improvewebpage build consistencyVSAvoidpage load speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent segments the webpage rendering process into two distinct parts: (1) server-side rendering that generates consistent HTML structure and critical content, and (2) client-side rendering that handles dynamic content and interactions. This segmentation allows the server to focus on generating consistent builds while the client handles performance-critical rendering operations, resolving the contradiction between build consistency and page load speed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements partial rendering where the server renders only the essential HTML structure and critical content needed for consistent builds, while leaving dynamic and non-critical content to be rendered by the client. This partial action on the server side maintains manufacturing precision for core content while improving productivity by reducing server processing time and resource consumption.

Inventive Principle:
Principle #16Partial or excessive action

2Productivity

If server-side rendering is used to optimize performance, then productivity is improved, but device complexity increases due to additional server infrastructure requirements

Engineering Contradiction:
Improvewebpage generation speedVSAvoidserver system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments rendering responsibilities between server and client, allowing the server to perform only essential rendering operations while the client handles dynamic content. This segmentation reduces the complexity burden on the server by offloading non-critical rendering tasks, thus improving productivity without excessively increasing server system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent makes the client device universal by enabling it to perform both rendering and interaction functions. The client not only displays content but also executes JavaScript to render dynamic content and handle user interactions, eliminating the need for complex server infrastructure to handle all rendering scenarios.

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

3Reliability

If complete webpage rendering is performed on the server, then reliability is improved, but loss of time increases due to extended server processing duration

Engineering Contradiction:
Improvewebpage display accuracyVSAvoidserver processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts dynamic and non-critical rendering tasks from the server process and transfers them to the client. The server focuses on generating reliable HTML structure while the client handles time-consuming dynamic content rendering, thus maintaining webpage display accuracy while reducing server processing time.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements preliminary server-side rendering of the essential HTML structure and critical content before transferring the page to the client. This preliminary action ensures that the core webpage content is rendered reliably and quickly on the server, while time-consuming dynamic content rendering is left for the client to perform after page load.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If dynamic content is rendered on the client side, then productivity is improved, but manufacturing precision deteriorates due to inconsistent rendering across different devices

Engineering Contradiction:
Improverendering efficiencyVSAvoidrendering consistency
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The patent segments content into static/critical portions rendered on the server for consistency and dynamic/non-critical portions rendered on the client for efficiency. This segmentation ensures that manufacturing precision is maintained for essential content while productivity is improved through client-side rendering of dynamic content.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different rendering qualities to different parts of the webpage: high manufacturing precision (server-side rendering) for critical content that must be consistent across devices, and optimized rendering (client-side rendering) for dynamic content where slight variations are acceptable. This local quality approach resolves the contradiction between rendering efficiency and consistency.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10839041B2Systems, method, and non-transitory computer-readable storage media for a partial-render operation generating code for displaying a webpage
Publication Date: 2020.11.17 WALMART APOLLO LLC
  • US10839041B2 patent drawing
  • US10839041B2 patent drawing
  • US10839041B2 patent drawing

AI summary

A system for use in displaying a webpage is described herein. The system includes a server computer that is configured to receive a request from a client computing device to display the webpage and identify application code associated with the webpage. The server computer initiates a partial-render operation including executing the application code to identify object data associated with the webpage, initiates service calls to a data library to retrieve the identified object data, and transmits the application code and the identified object data to the client computing device for use in displaying the webpage on the client computing device.