HTTP Request Merging with Boundary Identification for Progressive Rendering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
When a client merges HTTP requests to optimize performance, it must wait for all resources to be received from the server, leading to slow response times and delayed page rendering, as existing methods do not allow for the use of resources until all are fully transferred.
Innovation Solution
A method where a terminal merges multiple requests into a single request, detects the current status of the merged request, receives and processes resource data using boundary identifications, and stops receiving data once transfer is complete, enabling the client to utilize resources as they are received.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple HTTP requests are merged into a single request, then the number of requests is reduced and server pressure is decreased, but the client must wait for all resources to be received before using any of them, slowing down response time
Solution Approach 1:
The patent segments the merged resource data into individual resource units using boundary identifiers. Each resource can be independently extracted and processed as it becomes available, rather than waiting for the complete merged response. This segmentation allows the client to utilize resources progressively as they are received from the server.
Solution Approach 2:
The patent performs preliminary actions by pre-processing the merged resource data on the server side to insert boundary identifiers that mark the end of each resource. This preliminary structuring enables the client to quickly parse and extract individual resources without complex processing delays, allowing faster utilization of resources as they arrive.
2Loss of energy
If all resources are returned in a single merged response, then network overhead is reduced, but the client cannot process individual resources until the entire response is received
Solution Approach 1:
The patent divides the merged resource data into discrete resource segments using boundary identifiers. This segmentation allows the client to process and use individual resources as soon as they are received, without waiting for the complete merged response, thereby improving resource processing speed while maintaining efficient network bandwidth utilization.
Solution Approach 2:
The boundary identifiers act as intermediaries between the merged resource data and the client's resource processing logic. These markers enable the client to efficiently parse and extract individual resources from the merged response stream without requiring the entire response to be received first, thus improving processing speed while keeping network overhead low.
3Reliability
If the client waits for complete resource transfer before processing, then data integrity is ensured, but response time and page rendering speed are significantly reduced
Solution Approach 1:
The patent performs preliminary action by pre-structuring the merged resource data with boundary identifiers on the server side before transmission. This preliminary organization ensures data integrity is maintained while enabling the client to reliably extract and process individual resources as they arrive, without waiting for complete transfer, thus reducing page rendering time.
Solution Approach 2:
The boundary identifiers provide feedback mechanisms that allow the client to detect when individual resources have been completely received within the merged response stream. This feedback enables the client to process resources progressively as they become available while maintaining data integrity, rather than waiting for the entire merged response.
Data Source
Figure 1~2A
Figure 2B
Figure 3~4
AI summary
A method of processing a network request and response includes: merging a plurality of requests to obtain a merged request; transmitting the merged request to a server side; detecting a current status identification of the merged request; when the status indicated by the current status identification shows that data is transferring, receiving resource data corresponding to each request in the merged request and returned by the server side, and detecting the received resource data and obtaining a boundary identification contained in the received resource data; extracting and processing the resource data corresponding to each request in the merged request one by one according to the obtained boundary identification; and when the status indicated by the current status identification shows that the data transferring is completed, stopping receiving the resource data.