System and method for program execution

• US 7,685,230 B2
• Filed: 04/01/2004
• Issued: 03/23/2010
• Est. Priority Date: 04/01/2004
• Status: Expired due to Fees

• Current Assignee: Vaakya Technologies Private Limited
• Original Assignee: Vaakya Technologies Private Limited
• Inventors: Lakshminarasimhan Kanchi, Muralidharan
• Primary Examiner(s): WON, MICHAEL YOUNG
• Application Number:
  US10/816,493
• Publication Number:
  US 20050223356A1
• Time in Patent Office: 2,182 Days
• Field of Search: 709/203, 709/212, 709/219, 709/229, 709/246, 709/248, 709/202, 709/217, 709/230, 709/221, 717/107, 717/115, 717/121, 717/171, 717/168, 717/174
• US Class Current: 709/203
• CPC Class Codes: G06F 9/4484 Executing subprograms
• CPC Class Codes: G06F 9/45512 Command shells

Abstract

The invention pertains to a method and system that uses similar functionalities of different components within a software application when executing the application and application components. In one embodiment, predefined structures are created for a component type, where each component type has a similar functionality when executed. Parameter information is received at a client and linked with the predefined to provide a script specific predefined structure. The component is executed by executing the script specific predefined structure. After a user exits the component, the script specific predefined structure is automatically deleted.

Claims

1. A method for executing an application comprising components in a client-server environment, comprising:

sending a request for a component from a client to a server, wherein the component comprises a script and an associated predefined structure on the server, and wherein the client and the server have same runtime engine having same functional capabilities, and wherein the runtime engine includes a linker module and a plurality of predefined structures, and wherein the script associated with the component is created for use with runtime engine at the client or the server;

transmitting parameter information associated with the requested component by the server to the client, wherein the parameter information comprises the script associated with the requested component; and

linking the transmitted parameter information to a corresponding predefined structure at the client using the linker module in the runtime engine residing in the client to create an executable script specific predefined structure of the requested component, wherein the predefined structure having an intended functionality of the requested component, and wherein the linking step comprises locating identifiers within the script and inserting the component data corresponding to the identifiers into the predefined structure at the client by the linker module; and

executing the application using the script specific predefined structure of the component at the client.

2. The executing method of claim 1, further comprising searching for the requested component in the script at the server in response to the request for the component from the client.

3. The executing method of claim 1, further comprising determining an access level of a user of the client, wherein the transmitting step further comprises transmitting the parameter information based on the access level of the user.

4. The executing method of claim 1, further comprising storing the predefined structure at the client and storing a copy of the predefined structure at the server so that there is a client predefined structure and a server predefined structure.

5. The executing method of claim 1, further comprising automatically deleting the parameter specific predefined structure after the user has exited the component.

6. The executing method of claim 1, further comprising establishing a connection in response to the request for the component from the client, and the server creating a session identification number for the connection so that the client and the server can follow a connectionless protocol.

7. A system for executing an application comprising components in a client-server environment, comprising:

a client including a client memory, and a client processor, a client runtime engine configured to reside in the client memory, wherein the client runtime engine comprises a plurality of client predefined structures associated with the components and a linker module; and

a server including a server memory and a server processor, a server runtime engine configured to reside in the server memory, wherein the server runtime engine and the client runtime engine have same functional capabilities, and wherein the client runtime engine sends a request for a component to the server, and wherein the component comprises a script and an associated predefined structure on the server, and wherein the server runtime engine transmits parameter information associated with the requested component of the script to the client, and wherein the parameter information comprises the script associated with the requested component, and wherein the script associated with the component is created for use with the client runtime engine or the server runtime engine, and wherein the client runtime engine links the transmitted parameter information received from the server with a corresponding client predefined structure of the plurality of client predefined structures to create an executable script specific predefined structure, and wherein the predefined structure having an intended functionality of the requested component, and wherein the client runtime engine links the parameter information comprises locating identifiers within the script and inserting the component data corresponding to the identifiers into the predefined structure using the linker module, and wherein the client executes the application using the script specific predefined structure of the component.

8. The system of claim 7, wherein the client runtime engine comprises a client parser and a client execution engine, wherein the client execution engine comprises a client linker and the plurality of client predefined structures, wherein the client parser configured to instruct the client processor to search for identifiers within the parameter information transmitted by the server, wherein the client linker configured to instruct the client processor to link the parameter information to the client predefined structure to create the executable parameter specific predefined structure.

9. The system of claim 8, wherein the server runtime engine comprises a server parser and a server execution engine, the server execution engine comprises a server linker and a plurality of server predefined structures, a server predefined structure having an intended functionality corresponding to an intended functionality of a component type of a plurality of component types, wherein the component has the intended functionality of the component type, the server parser configured to instruct the server processor to search for the component in the script, the component being requested by the client, the server linker configured to instruct the server processor to link the parameter information to a corresponding server predefined structure to provide a specific predefined structure;

and a server transceiver being configured to transmit the parameter information associated with the component of the script.

10. The system of claim 7, wherein client memory further comprises a client long term memory and a client short term memory, the client runtime engine being stored in the client long term memory before the client sends the request for the component of the script, wherein the client processor is configured to transfer the client runtime engine to the client short term memory when the client sends the request for the component of the script, to temporarily store the executable parameter specific predefined structure in the client short term memory, and to automatically delete the executable parameter specific predefined structure from the client short term memory when the client exits the component.

11. The system of claim 7, wherein the parameter information transmitted by the server includes identifiers associated with component information and the predefined structure includes the corresponding identifiers.

12. The system of claim 7, wherein the server creates a unique session identification number for every connection established to uniquely identify each connection and recreate the session previously established thereby facilitating a connectionless protocol.

13. An application for executing a component when a user accesses a component on a system in a client-server environment, the application comprising:

a runtime engine comprising an execution engine comprising a plurality of predefined structures and a linker, a predefined structure of the plurality of predefined structures having an intended functionality of a component type of a plurality of component types, wherein the component has the intended functionality of the component types, wherein the component comprises a script and an associated predefined structure on a server, and wherein the script associated with the component is created for use with the runtime engine and wherein when the user accesses the component;

(a) the linker instructs a client processor to link parameter information associated with the component to a corresponding predefined structure to create an executable script specific predefined structure, wherein the parameter information associated with the component is transmitted from the server to a client upon user access and stored in a client processor readable memory, and wherein the server and the client have the runtime engine functional capabilities, and wherein the parameter information comprises the script associated with user access, and wherein linking the parameter information by the client processor comprises locating identifiers within the script and inserting the component data corresponding to the identifiers into the predefined structure; and

(b) the execution engine instructs the client processor to execute the executable script specific predefined structure to execute the component;

wherein the runtime engine is stored in a media and the runtime is transferred to the client processor readable memory of a system including the client processor readable memory and the client processor when the media is used with the system.

14. The application of claim 13, wherein the system comprises a server, the server comprising a server processor readable memory, a server transceiver, a server processor and a server runtime engine, wherein the server runtime engine is transferred to a server processor readable memory of the system and the server runtime engine comprises a copy of the runtime engine, wherein the server runtime engine comprises a server parser and a server execution engine, wherein a user at the client requests a component from the server prior to running the component and, when the user requests the component:

(a) the server parser instructs the server processor to search for the component in the script, the script being stored in the server processor readable memory, and

(b) the execution engine instructs the server processor to transmit the parameter information associated with the component of the script to the client via the server transceiver.

15. The application of claim 14, wherein the server execution engine further comprises a plurality of server predefined structures, a server predefined structure of the plurality of server predefined structures having the intended functionality of a component type of the plurality of component types, wherein the component requested by the user has the intended functionality of the component type.

16. The application of claim 15, wherein, when the client requests the component, the server execution engine instructs the server processor to create a session number and to transmit the session number to the client.

17. The application of claim 13, wherein the execution engine instructs the client processor to store the executable parameter specific predefined structure in the client processor readable memory and instructs the processor to automatically delete the executable parameter specific predefined structure from the memory after the user exits the component.