Edge Server Static HTML Delivery Reduces Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web page assembly methods at runtime lead to increased latency and inefficiencies, as HTML files are generated on the server and transmitted to the client, requiring dynamic back-end tools for updates, which can slow down page delivery and complicate development.
Innovation Solution
Implementing an edge server that receives compiled static web pages and components from a compiling machine, allowing for direct delivery to the client browser, reducing latency by generating HTML at build time and using tools like node.js, Grunt, Sass, and Handlebars to manage content and configuration, enabling streamlined framework-level modifications and client-side execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If HTML files are generated on the server at runtime using dynamic back-end tools, then content can be updated and delivered to clients, but latency time increases and page delivery is slowed down
Solution Approach 1:
The patent applies preliminary action by pre-compiling HTML files at build time using static site generation tools (e.g., Jekyll, Hugo, Gatsby) before deployment. These pre-compiled static HTML files are then served directly by the edge server without runtime server-side processing, eliminating the latency associated with dynamic HTML generation and significantly accelerating page delivery to clients.
2Ease of manufacture
If dynamic back-end tools are used to build HTML files, then content can be modified centrally, but device complexity and development complexity increase
Solution Approach 1:
The patent employs copying by using template-based static site generation where content is separated into reusable templates and data files. These templates are copied and instantiated multiple times to generate final HTML pages. This approach simplifies content updates by allowing developers to modify templates or data files without affecting the entire system, reducing both device complexity and development complexity while maintaining ease of content manufacturing.
3Loss of time
If HTML assembly is performed on the front end, then latency time is reduced, but client-side processing requirements increase
Solution Approach 1:
The patent extracts the HTML assembly process from the server environment and relocates it to the client browser through static site generation. Pre-compiled static HTML files containing all necessary content and structure are delivered to the client, where they are assembled and rendered without requiring server-side processing. This extraction reduces latency while the standardized nature of static HTML keeps client-side processing simple and accessible.
Data Source
AI summary
Apparatus and methods for providing content to a client browser. The methods may include providing a web page compiling machine. The methods may include providing an edge server that interfaces between the compiling machine and the client browser. The edge server may include a web server. The methods may include receiving at the edge server, from the compiling machine, a first compiled static web page that includes an instruction, executable by the client browser, for determining a client configuration parameter. The methods may include delivering, from the edge server, the first compiled static web page component to the client browser. The methods may include receiving, at the edge server, from the client browser a request for a compiled static web page component that corresponds to the parameter.