Client-side script to application communication system

• US 20040019626A1
• Filed: 07/26/2002
• Published: 01/29/2004
• Est. Priority Date: 07/26/2002
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Shepherd, David R., Soroka, David M., Sibert, Mark A.
• Granted Patent: US 9,357,013 B2
• Time in Patent Office: Days
• US Class Current: 709/202
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A method of activating external application logic from a script embedded in client-side rendered markup. The method can include establishing a communicative link with an application interface to the script. A pre-configured message can be received from the application interface over the communicative link. In response to receiving the pre-configured message, at least one operation can be activated in a process address space which is separate from a process address space used to render the markup and to process the script. Importantly, in a preferred aspect of the present invention, data can be retrieved from a data source remote to the client computing device. Subsequently, the retrieved data can be used to populate at least one user interface field in separately rendered markup.

Claims

1. In a client computing device, a method of activating external application logic from a script embedded in client-side rendered markup, the method comprising the steps of:

responsive to processing the script embedded in the client-side rendered markup, locating the external application logic in the client computing device;

establishing a communicative link with said located external application logic; and

, activating at least one operation in said located external application logic over said communicative link.

2. The method of claim 1, wherein said establishing step comprises the step of connecting to said located external application logic on a pre-configured port.

3. The method of claim 1, wherein said activating step comprises the steps of:

determining a handle to a message handling routine for said located external application logic; and

, forwarding a pre-configured message to said located external application logic using said handle.

4. The method of claim 1, further comprising the steps of:

receiving data from said located external application programming logic; and

,

processing said received data in the script.

5. The method of claim 4, wherein said processing step comprises the step of populating at least one user interface field with said received data.

6. In a client computing device, a method of activating external application logic from a script embedded in client-side rendered markup, the method comprising the steps of:

establishing a communicative link with an application interface to the script;

receiving a pre-configured message from said application interface over said communicative link; and

,

responsive to receiving said pre-configured message, activating at least one operation in a process address space in the client computing device which is separate from a process address space used to render the markup and to process the script.

7. The method of claim 6, wherein said establishing step comprises the step of connecting to said script on a pre-configured port.

8. The method of claim 6, wherein said activating step comprises the steps of:

matching said pre-configured message with a coded message handling routine; and

,

performing computing operations associated with said coded message handling routine.

9. The method of claim 6, further comprising the steps of:

retrieving data from a data source remote to the client computing device; and

,

populating at least one user interface field in separately rendered markup with said retrieved data.

10. A machine readable storage having stored thereon a computer program for activating external application logic from a script embedded in client-side rendered markup, the computer program comprising a routine set of instructions which when executed cause the machine to perform the steps of:

responsive to processing the script embedded in the client-side rendered markup, locating the external application logic;

establishing a communicative link with said located external application logic; and

, activating at least one operation in said located external application logic over said communicative link.

11. The machine readable storage of claim 10, wherein said establishing step comprises the step of connecting to said located external application logic on a pre-configured port.

12. The machine readable storage of claim 10, wherein said activating step comprises the steps of:

determining a handle to a message handling routine for said located external application logic; and

,

forwarding a pre-configured message to said located external application logic using said handle.

13. The machine readable storage of claim 10, further comprising the steps of:

receiving data from said located external application programming logic; and

,

processing said received data in the script.

14. The machine readable storage of claim 13, wherein said processing step comprises the step of populating at least one user interface field with said received data.

15. A machine readable storage having stored thereon a computer program for activating external application logic from a script embedded in client-side rendered markup, the computer program comprising a routine set of instructions which when executed cause the machine to perform the steps of:

establishing a communicative link with an application interface to the script;

receiving a pre-configured message from said application interface over said communicative link; and

,

responsive to receiving said pre-configured message, activating at least one operation in a process address space which is separate from a process address space used to render the markup and to process the script.

16. The machine readable storage of claim 15, wherein said establishing step comprises the step of connecting to said script on a pre-configured port.

17. The machine readable storage of claim 15, wherein said activating step comprises the steps of:

matching said pre-configured message with a coded message handling routine; and

,

performing computing operations associated with said coded message handling routine.

18. The machine readable storage of claim 15, further comprising the steps of:

retrieving data from a data source remote to the client computing device; and

,

populating at least one user interface field in separately rendered markup with said retrieved data.