System and method for integration of browser-based thin client applications within desktop rich client architecture
First Claim
1. A method for facilitating the reuse of a browser-based thin client of a client-server application in a browser-independent context, the method comprising:
- receiving, by a computer system, first program code for the browser-based thin client, wherein the first program code has one or more browser dependencies that require the browser-based thin client to operate within a web browser in order to interact with a server side of the client-server application, wherein the one or more browser dependencies comprise one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application; and
converting, by the computer system, the first program code for the browser-based thin client into second program code for a browser-independent client application that is a rich-client application configured to be invoked and run from a rich-client infrastructure,wherein the converting comprises generating additional program code based at least in part on the first program code, the additional program code to be included in the second program code to facilitate reuse of the browser-based thin client within the rich-client infrastructure,wherein the second program code does not contain the one or more browser dependencies, so that the browser-independent client application is no longer dependent on a presence of the web browser in order to function, andwherein the converting further comprises;
determining, by the computer system, the one or more browser dependencies, the determining comprising identifying the one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application; and
eliminating, by the computer system, the one or more browser dependencies, the eliminating comprising eliminating the one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application.
1 Assignment
0 Petitions
Accused Products
Abstract
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.
-
Citations
17 Claims
-
1. A method for facilitating the reuse of a browser-based thin client of a client-server application in a browser-independent context, the method comprising:
-
receiving, by a computer system, first program code for the browser-based thin client, wherein the first program code has one or more browser dependencies that require the browser-based thin client to operate within a web browser in order to interact with a server side of the client-server application, wherein the one or more browser dependencies comprise one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application; and converting, by the computer system, the first program code for the browser-based thin client into second program code for a browser-independent client application that is a rich-client application configured to be invoked and run from a rich-client infrastructure, wherein the converting comprises generating additional program code based at least in part on the first program code, the additional program code to be included in the second program code to facilitate reuse of the browser-based thin client within the rich-client infrastructure, wherein the second program code does not contain the one or more browser dependencies, so that the browser-independent client application is no longer dependent on a presence of the web browser in order to function, and wherein the converting further comprises; determining, by the computer system, the one or more browser dependencies, the determining comprising identifying the one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application; and eliminating, by the computer system, the one or more browser dependencies, the eliminating comprising eliminating the one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17)
-
-
15. A system for facilitating the reuse of a browser-based thin client of a client-server application in a browser-independent context, the system comprising:
-
a storage component configured to store program code for the browser-based thin client; and a processing component in communication with the storage component, wherein the processing component is configured to; convert first program code for the browser-based thin client into second program code for a browser-independent client application that is a rich-client application configured to be invoked and run from a rich-client infrastructure, wherein the converting comprises generating additional program code based at least in part on the first program code, the additional program code to be included in the second program code to facilitate reuse of the browser-based thin client within the rich-client infrastructure, wherein the first program code has one or more browser dependencies that require the browser-based thin client to operate within a web browser in order to interact with a server side of the client-server application, wherein the one or more browser dependencies comprise one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application, wherein the second program code does not contain the one or more browser dependencies, so that the browser-independent client application is no longer dependent on a presence of the web browser in order to function, and wherein the converting further comprises; determining the one or more browser dependencies, the determining comprising identifying the one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application; and eliminating the one or more browser dependencies, the eliminating comprising eliminating the one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application.
-
-
16. A non-transitory machine-readable medium for a computer system, the non-transitory machine-readable medium having stored thereon a series of instructions which, when executed by a processing component, cause the processing component to facilitate the reuse of a browser-based thin client of a client-server application in a browser-independent context by:
-
receiving program code for the browser-based thin client, wherein the program code for the browser-based thin client has one or more browser dependencies that require the browser-based thin client to operate within a web browser in order to interact with a server side of the client-server application, wherein the one or more browser dependencies comprise one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application; and converting the program code for the browser-based thin client into browser-independent program code for a rich-client application configured to be invoked and run from a rich-client infrastructure, wherein the converting comprises generating additional program code based at least in part on the program code, the additional program code to be included in the browser-independent program code to facilitate reuse of the browser-based thin client within the rich-client infrastructure, wherein the browser-independent program code does not contain the one or more browser dependencies, so that the browser-independent client application is no longer dependent on a presence of the web browser in order to function, and wherein the converting further comprises; determining the one or more browser dependencies, the determining comprising identifying the one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application; and eliminating the one or more browser dependencies, the eliminating comprising eliminating the one or more dependencies that require the browser-based thin client to depend on the web browser to handle application security when interacting with the server side of the client-server application.
-
Specification