Mock Upload Event Generator for Selective File Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current browser-based systems lack the capability to modify file upload events, such as allowing or blocking specific files or directories during an upload operation, and cannot perform actions like encrypting or renaming files before uploading, as they either transmit all files or deny all files in a single upload event.
Innovation Solution
A client computing device system is introduced that includes a mock upload event generator, dispatcher, and event handler to create and propagate mock upload events and data transfer objects, allowing for the modification of upload events before actual transmission, including the ability to intercept and analyze received upload events, perform logic on them, and send queries to a proxy server for instructions on how to process or deny files based on upload policies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the system transmits all files or denies all files in a single upload event, then the upload operation is simple and fast, but the ability to selectively upload specific files or apply different processing to different files is lost
Solution Approach 1:
The patent segments the upload event into individual file-level events by introducing a mock upload event generator that creates separate upload events for each file within a directory. This allows the system to process files individually rather than as a single batch, enabling selective uploading and different processing for different files while maintaining overall upload efficiency.
Solution Approach 2:
The patent introduces a mock upload event generator as an intermediary component between the original upload event and the file processing system. This intermediary generates mock upload events that contain file information and enables the system to intercept, analyze, and selectively process files before actual upload, resolving the contradiction between simplicity and adaptability.
2Adaptability or versatility
If the system allows modification of upload events, then selective file upload and processing capability is improved, but the complexity of the upload handling system increases
Solution Approach 1:
The patent uses a mock upload event generator that creates copies (mock events) of the original upload events. These mock events contain the necessary file information and can be processed independently, allowing the system to modify and analyze upload events without altering the actual upload process, thus reducing complexity while maintaining adaptability.
Solution Approach 2:
The system performs preliminary actions by generating and processing mock upload events before the actual file upload occurs. This allows the system to intercept, analyze, and make decisions about which files to upload and how to process them in advance, reducing the complexity of real-time decision-making during the actual upload operation.
3Reliability
If the system intercepts and analyzes upload events to apply policies, then security and compliance are improved, but the time required for upload processing increases
Solution Approach 1:
The patent implements preliminary action by intercepting and analyzing upload events before the actual file transmission occurs. The system generates mock upload events that can be quickly processed to determine policy compliance, making upload decisions in advance and avoiding time-consuming analysis during the actual upload process.
Solution Approach 2:
The system extracts and processes only the necessary information from upload events by creating mock events that contain minimal required data. This extraction approach allows the system to analyze and make policy compliance decisions quickly without processing the entire file content, thus reducing time loss while maintaining reliability.
Data Source
AI summary
Methods and systems are provided for a client computing device including a browser that renders a web page. Program code generates a mock upload event and a corresponding mock data transfer object for uploading data using the web page. The mock upload event and the corresponding mock data transfer object are propagated to an upload event listener of the web page and executed. Prior to generating the mock upload event and corresponding mock data transfer object, an embedded upload event listener may receive an upload event, read the upload event, drop the received upload event from an event handler pipeline, and call synchronously or asynchronously, code to perform logic on the received upload event for the generation of the mock upload event and a corresponding mock data transfer object.