Composite File Download Progress Tracking via Notification Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users downloading composite files from cloud storage services, such as ZIP files, lack individual file progress information and error notifications due to the web browser's unawareness of file sizes and download orders within the composite file.
Innovation Solution
A system comprising a media server and a notification server that transmits progress information, including the number of files downloaded and any errors, to a user device, allowing for the display of detailed download progress within the browser application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If composite files are compressed and transmitted as a single file, then transmission efficiency is improved, but individual file progress information is lost
Solution Approach 1:
The media server sends progress information to the notification server, which then provides feedback to the user device. This feedback mechanism includes the number of files transmitted, total files in the composite, and error information, allowing users to track individual file download status without compromising transmission efficiency.
Solution Approach 2:
The notification server acts as an intermediary between the media server and the user device. It receives progress information from the media server, processes it to determine user session context, and forwards relevant progress information to the user device, thereby preserving individual file progress information while maintaining efficient composite file transmission.
2Ease of operation
If the web browser handles composite file downloads, then ease of operation is improved, but access to individual file progress information is lost
Solution Approach 1:
The notification server serves as an intermediary that bridges the web browser's simple download interface and the need for detailed progress information. It receives progress data from the media server and delivers it to the user device for display within the browser application, maintaining ease of operation while providing individual file progress tracking.
Solution Approach 2:
A feedback loop is established where the media server reports progress to the notification server, which then feeds this information back to the user device. This allows the browser to continue handling downloads simply while users can access detailed progress information about individual files within the composite.
3Loss of information
If progress information is transmitted separately from the composite file, then individual file tracking is improved, but system complexity increases
Solution Approach 1:
The notification server performs multiple functions: it manages user sessions, receives progress information from the media server, processes this information to determine relevant user context, and forwards progress updates to user devices. This multi-functionality consolidates complexity into a single component rather than distributing it across multiple systems.
Solution Approach 2:
By introducing the notification server as an intermediary, the system manages complexity through a dedicated component that handles all progress information processing. This centralizes the complexity of tracking individual file progress while keeping the media server and user device relatively simple in their respective roles.
Data Source
AI summary
Systems and methods for tracking the download progress of a composite file. One system includes a notification server and a media server. The notification server provides a token to a user device that uniquely identifies a user session between a browser application and a cloud storage service. The media server receives the token from the browser application associated with a download request for a set of files, creates a composite file including the set of files, transmits the composite file to the user device, and, while transmitting the composite file, transmits progress information and the token to the notification server. The progress information includes a number of files in the composite file transmitted to the user device. The notification server receives the progress information and the token from the media server, determines the user session based on the token, and transmits the progress information to the user device.