Browser-independent Client Integration via Code Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Reusing browser-based thin clients in browser-independent contexts is challenging due to dependencies on web browser features for security, file handling, and parameter passing, which hinder integration into desktop-based rich client infrastructures.
Innovation Solution
A conversion utility automatically converts browser-based thin client program code to eliminate dependencies on web browsers, enabling the thin client to operate independently by integrating security handling and file management directly into the client application, and managing parameters internally.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If browser-based thin client program code is reused directly in a browser-independent context, then development time is reduced, but the application cannot operate without a web browser due to browser dependencies
Solution Approach 1:
The conversion utility extracts browser-specific dependencies (cookies, HTML forms, browser file handling) from the thin client program code and removes them, allowing the application to function independently of a web browser while preserving the original program code structure
Solution Approach 2:
A conversion utility acts as an intermediary tool that automatically transforms browser-dependent thin client code into browser-independent code, bridging the gap between existing web-based applications and desktop rich client requirements
2Device complexity
If browser features are used to handle security and file management, then implementation complexity is reduced, but security control and file handling efficiency deteriorate in browser-independent contexts
Solution Approach 1:
The converted thin client application performs security handling and file management operations itself without relying on browser services, making the application self-sufficient and improving security control while maintaining implementation simplicity through automated conversion
3Productivity
If existing browser-based thin clients are used as-is, then integration speed is improved, but integration capability into desktop rich client infrastructure deteriorates
Solution Approach 1:
The conversion utility changes the operational parameters of the thin client program code by removing browser-specific functionality and adapting it to desktop application standards, enabling seamless integration into rich client infrastructure while maintaining fast integration speed
Data Source
AI summary
Techniques for facilitating the reuse of a browser-based thin client of a client-server application in a browser-independent context. These techniques may be used, for instance, to integrate the functionality of a browser-based thin client in a desktop-based, rich client infrastructure. In one set of embodiments, these techniques include determining one or more browser dependencies that require the thin client to operate within a web browser. For example, the thin client may depend on a web browser to handle application security, the loading/caching of client-side files, the receipt/passing of application parameters, and the like. These browser dependencies are then eliminated. As a result, the thin client can be subsequently reused without the presence of a web browser. In one set of embodiments, this process is performed by a conversion utility that automatically converts program code for the browser-based thin client into program code for a browser-independent client application.