Asynchronous Web Content Delivery via Background Processes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
End-users face challenges with slow and interrupted web content downloads due to synchronous processes, which require restarting from the beginning if interrupted, and are locked to a specific device, impacting performance and availability across different devices.
Innovation Solution
Implementing web content delivery via asynchronous background processes, where the content is sent from a content server to a customer storage server and then to the end-user device, allowing for independent foreground tasks and seamless resume in case of interruptions, and enabling access across multiple devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If synchronous download process is used, then download control is simple, but user cannot perform other tasks during download and download time is long
Solution Approach 1:
The system transitions from a synchronous static download process to an asynchronous dynamic process. The download manager operates independently in the background, allowing the user interface to respond to other user actions while the download continues. This dynamic separation enables the user to perform multiple tasks simultaneously without compromising download control.
Solution Approach 2:
The asynchronous download process ensures continuous progress of the download task without blocking the user interface. The download manager maintains persistent connection and continues transferring data even when the user switches tasks, eliminating the interruption caused by synchronous processing.
2Device complexity
If synchronous download process is used, then download process is simple, but download must restart from beginning if interrupted
Solution Approach 1:
The system performs preliminary actions by maintaining download state information and progress tracking in the download manager before interruptions occur. When an interruption happens, the recorded progress data enables the download to resume from the exact point of interruption rather than restarting from the beginning.
Solution Approach 2:
The download manager implements feedback mechanisms to track download progress, connection status, and transfer state. This feedback information is stored and used to manage resume operations, allowing the system to recover from interruptions efficiently by utilizing the recorded progress state.
3Ease of operation
If web content is locked to specific device, then device-specific control is simple, but content is not available on other devices
Solution Approach 1:
The system implements universality by enabling the same web content to be accessed across multiple different devices. The download manager and content delivery system are designed to work with various device types, allowing users to retrieve content from any registered device rather than being limited to a single device.
Solution Approach 2:
The system introduces an intermediary mechanism that mediates between the content source and the user device. This intermediary layer manages the content delivery independently of the specific device used, enabling content to be transferred to different devices while maintaining control over the distribution process.
4Device complexity
If centralized download server is used, then content management is simple, but global end-users experience slow download speed
Solution Approach 1:
The system segments the centralized download server into multiple distributed components. Instead of a single centralized server handling all global requests, the system divides content delivery into separate segments that can be served from different locations, reducing the distance and complexity for global users.
Data Source
AI summary
Sending web content via asynchronous background processes is described. A system receives, from a webserver, a request, from an end-user device, for web content. The system sends the web content from a content server to a customer storage server associated with the end-user device. The system sends the web content from the customer storage server to the end-user device via an asynchronous background process.