Local Agent Asynchronous Remote File Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote file access systems require a persistent connection and are limited in providing seamless access to files from remote locations, often relying on real-time connections and specific software setups, which can be cumbersome and inefficient.
Innovation Solution
A remote file access system utilizing a local agent architecture with a transmission control protocol/internet protocol stack, an extensible markup language input/output parser, and a simple object access protocol interpreter, enabling asynchronous communication and periodic connections to a server for task requests and file retrieval, along with a remote client that sends task requests and receives notifications for file transfer instructions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a persistent real-time connection is maintained between client and server, then file access reliability is improved, but connection maintenance complexity and energy consumption increase
Solution Approach 1:
The system implements periodic polling where the local agent connects to the server at predetermined intervals to check for task requests and file updates. This replaces the need for continuous persistent connections while maintaining file access reliability, as the agent periodically synchronizes with the server to retrieve new tasks and upload completed files.
Solution Approach 2:
The local agent autonomously manages connection initiation and task execution without requiring continuous server-initiated connections. The agent self-starts periodic connections, automatically retrieves task requests, executes local tasks, and uploads results, reducing the complexity of connection maintenance while ensuring reliable file access.
2Reliability
If special software and real-time connections are required for remote file access, then file access control and security are improved, but ease of operation and system simplicity deteriorate
Solution Approach 1:
The system divides functionality into distinct components: the server manages task request distribution and file storage, while the local agent handles task execution and periodic synchronization. This segmentation allows the server to maintain security controls through centralized task management while the lightweight agent provides simple client-side operation without requiring complex real-time connection software.
Solution Approach 2:
The server acts as an intermediary that receives task requests from remote clients and distributes them to local agents. This intermediary architecture enables controlled file access through centralized authorization while allowing simple agent implementations that periodically connect without requiring complex real-time communication software on client devices.
3Device complexity
If periodic connections are used instead of persistent connections, then connection maintenance burden is reduced, but file access speed and responsiveness may worsen
Solution Approach 1:
The server pre-processes and queues task requests before the local agent connects. When the agent periodically connects, it immediately retrieves ready-to-execute tasks without waiting, and the server has already prepared task descriptions and parameters. This preliminary action ensures fast file access during periodic connections while maintaining low connection maintenance burden.
Solution Approach 2:
The server continuously processes and queues task requests in the background, maintaining useful action even when the local agent is not connected. This ensures that when the agent does connect periodically, it can immediately retrieve and execute tasks without delay, maintaining effective file access speed while using periodic rather than persistent connections.
Data Source
AI summary
Systems and methods for remote file access are disclosed. According to an embodiment, a local agent polls a server for a task request at a polling interval scheduled by a schedule timer in accordance with a set of local agent and remote client preferences. The local agent is responsible for executing a task from the task request and causing a file to be uploaded to the server. The local agent uses a task processor for polling a server, a schedule timer for controlling polling, and one or more protocol stacks, such as TCP/IP and SOAP, for communicating with the server. The local agent can also interface with a MAPI database for message delivery.