Remote Screen File Deployment for Low-Hardware Clients
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing server software requires robust hardware on remote clients to handle complex data interactions, such as interactive menu systems, and lacks security and customizable event handling, making it unsuitable for industries with limited technological resources, like the insurance industry, where sensitive data is involved.
Innovation Solution
A system that deploys small, serialized binary screen files to remote clients, allowing them to interact with server-side application software without extensive local processing, while securely handling and customizing events, thereby reducing hardware demands and enhancing security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If CGI or scripting language files are sent to enable robust interaction, then interaction capability is improved, but hardware requirements and complexity increase
Solution Approach 1:
The patent introduces screen files as an intermediary format that bridges the server and client. These screen files contain pre-processed display information and event handling logic, allowing the client to render complex interfaces without requiring powerful local processing capabilities. The screen files act as a mediator that translates server data into client-ready display formats.
Solution Approach 2:
The server performs preliminary processing by generating screen files that contain pre-computed display information, layout data, and event handling instructions. This preliminary action transfers the computational burden from the client to the server, allowing clients with limited hardware capabilities to display complex interactive interfaces without local processing power.
2Adaptability or versatility
If CGI or scripting language files are used for complex menu display, then display capability is improved, but processing burden on client increases
Solution Approach 1:
Screen files serve as an intermediary that contains pre-processed display information for complex menus and interfaces. The screen files include all necessary layout, styling, and interaction logic, allowing the client to render complex displays without performing heavy processing. The intermediary screen file format separates display logic from processing logic.
Solution Approach 2:
The server creates copies of display information in screen file format that contain all necessary rendering data. Instead of sending raw data and requiring the client to process and generate display information, the server provides pre-formatted copies ready for direct rendering, significantly reducing client processing burden.
3Adaptability or versatility
If standard executable files are sent for remote display, then functionality is improved, but security is worsened
Solution Approach 1:
The patent changes the format parameter of remote display files from standard executable formats to a proprietary screen file format. This parameter change enables the files to be processed by a dedicated screen file processor rather than general-purpose executable interpreters, improving security while maintaining functionality. The new format includes built-in security characteristics.
Solution Approach 2:
Screen files are designed as disposable, stateless objects that are processed and discarded. Each screen file contains all necessary information for a specific display state and is processed by the screen file processor without being stored or reused. This disposable nature eliminates security vulnerabilities associated with persistent executable files while maintaining full functionality.
Data Source
AI summary
A system and method for remotely displaying screen files and for trapping a customized set of operator input is disclosed. A server generates and deploys a plurality of screen files to a remote client. The screen files each include a plurality of display control elements and a list of events to be trapped and forwarded to the server. The list of events may be optimized for each particular screen file. The remote client displays the plurality of display control elements and stores the list of events. For any event that occurs which is included in the list of events, such as a submit data event, the remote client sends data indicative of the event to the server. The server interprets the data indicative of the occurrence of the event, processes the event, and, if appropriate, generates and sends a command to update the displayed representation of the screen file.