Method and protocol for mediating communication between software applications

Abstract

A method and protocol suitable for mediating communication between an application written in a platform independent language, running on a specific processor or computing platform, and an application written in the processor's native language. As part of the present invention, an application written in a platform independent code may be compiled and/or linked to a first mediation module and an application written in the processor's native code may be compiled and/or linked to a second mediation module The first and second mediation modules may communicate with each other utilizing a stream protocol providing for communication of various data types, including but not limited to function calls, function parameters, function results, and event notification.

Description

FIELD OF THE INVENTION

[0002] The present invention relates generally to the field of computer software applications. More specifically, the present invention relates to a method and protocol for mediating communication between software applications.

BACKGROUND OF THE INVENTION

[0003] Portability of software applications between computing platforms has been an issue among software developers and users since beginning of the software industry. Platform independent languages such as Java have been developed in order to address this issue. However, Java and other languages claiming to be platform independent require an interpreter running on the same computing platform so as to convert the platform independent code into instructions the processor upon which the code is running on can understand and execute. Because of the requirement for an additional level of processing, i.e. interpreting, code written in Java and other platform independent languages typically runs less efficiently and requires relatively greater resources than code performing the same function in a processor's native language, code compiled specifically for the processor the code is running on. Therefore, code written in Java or another platform independent language usually runs slower than functionally equivalent code in a processor's native language, machine language produced by a compiler.

[0004] One solution for speeding up the performance of applications written in platform independent languages is to offload some operations to concurrently running applications written in the processor's native language and to use a mediation protocol to interact between the two applications.

SUMMARY OF THE INVENTION

[0005] The present invention is a method, system and protocol for mediating communication between a first and second software application. As part of the present invention, an application written in a first computer language may be compiled and/or linked to a first mediation module and an application written in a second computer language may be compiled and/or linked to a second mediation module. The first and second mediation modules may communicate with each other utilizing one or more protocols, providing for communication of various data types. including but not limited to function calls, function parameters, function results, and event notification.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:

[0007] FIG. 1 Shows a diagrammatic illustration of two applications linked to and communicating through two mediation modules according to the present invention;

[0008] FIG. 2 Shows a flow diagram illustrating the steps of by which a first application calls a function of a second function using the mediation modules of the present invention; and

[0009] FIG. 3 Shows a diagrammatic illustration of a first application using several mediation modules.

[0010] It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.

DETAILED DESCRIPTION

[0011] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present invention.

[0012] Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as “processing”, “computing”, “calculating”, “determining”, or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices.

[0013] Embodiments of the present invention may include apparatuses for performing the operations herein. This apparatus may be specially constructed for the desired purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs) electrically programmable read-only memories (EPROMs). electrically erasable and programmable read only memories (EEPROMs), magnetic or optical cards or any other type of media suitable for storing electronic instructions, and capable of being coupled to a computer system bus.

[0014] The processes and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the desired method. The desired structure for a variety of these systems will appear from the description below. In addition, embodiments of the present invention are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the inventions as described herein.

[0015] The present invention is a method, system and protocol suitable for mediating communication between an application written in a platform independent language, running on a specific processor or computing platform, and an application written in the processor's native language. As part of the present invention, an application written in a platform independent code may be compiled and/or linked to a first mediation module and an application written in the processor's native code may be compiled and/or linked to a second mediation module. The first and second mediation modules may communicate with each other utilizing a stream protocol providing for communication of various data types, including but not limited to function calls, function parameters, function results, and event notification.

[0016] Turning now to FIG. 1, there is shown a first application 100 linked to a first mediation module 120, both of which may run in a single process. A second application 200 is linked to a second mediation module 220. The first and second mediation modules may communicate with one another utilizing a stream protocol. In an embodiment of the present invention, the first application 100 is written in a platform independent language, e.g. Java, and the first mediation module 120 causes the second application 200, written in the processor's native code, erg. C, to be launched. The first mediation module 120 may issue a command causing the operating system to produce an instance of the second application 200 and the second mediation module 220.

[0017] The first application 100 may pass a function call to the second application 200 through the first 120 and second 220 mediation modules, respectively. The second application 200 may pass the results of the function to the first application 100, also through the first 120 and second 220 mediation modules. In addition to passing function calls and their associated parameters, each of applications, 100 and 200, may also pass function results and event notification to the other. In one embodiment of the present invention, the application written in a platform independent or interpreted language passes a function call to an application written in the processors native code.

[0018] Turning now to FIG. 2, there is shown a flow chart with the steps of a method according to the present invention by which a first application passes a function call to a second application. As part of step 1000, a first application 100 issues a function call for a function contained within a second application 200. The first application's function call and associated parameters are passed to a first mediation module 120 where they are translated into a stream protocol and transmitted, Step 2000. The function call and associated parameters, in the stream protocol format are received by the second mediation module 220 and translated into a format suitable for the second application 200 (Step 3000). The second application 200 may return a value, a series of values, or some other result (Step 4000), The results may take a reverse path back the first application 100, that is, through the second mediation module (step 5000) and through the first mediation module (step 6000). The first application 100 may receive the result in its own format (step 7000) once the first mediation module 120 converts the results from the stream protocol (step 6000).

[0019] Communication between mediation modules occurs using a stream protocol or other protocol that may provide ordered delivery of data over multiple streams, for example TCP/IP streams. A mediation protocol may be used over a communications protocol to form a stream protocol according to the present invention.

[0020] The following is an example of functions performed by a mediation protocol according to the present invention:

[0021] 1. The first application may launch the second, providing it, by means of command-line arguments (or other mechanism) with numbers of two TCP/IP ports to be used for communication between the two applications. The first port number is termed the Command Port and the second the Event Port.

[0022] 2. The second application, when launched, stores the command port number and event port number for future reference in a place accessible to its mediation module.

[0023] 3. When the second application first attempts to perform an operation using its mediation module, it opens up a stream for event notifications by connecting a TCP/IP client socket to the event port. This is termed the Event Stream.

[0024] 4. When the second application requires that a function call be made through its mediation module, the following steps arc performed:

[0025] a. If this is the first time that a function call has been made from the system thread from which the call is made, a new stream connection is opened up for the exclusive use of this thread. This is done by connecting a TCP/IP client socket to the command port, Details of this connection are then stored for future reference. Each such stream connection has its own memory buffers, and calls through one such stream connection are executed independently of calls though another connection. This ensures thread-safety of the system.

[0026] b. If this is not the first time that a function call has been made from the current system thread, the second application's mediation module looks up a connection it has previously stored for this thread, and uses this connection.

[0027] c. In order to call a function, the second application first needs a reference to the function to be called. This may have been stored from a previous use of the function, or may be acquired as follows:

[0028] i. The second application's mediation module sends a request for a function reference number to the mediation module of the first application. The request includes the package name, class name and method name of a static Java method to be invoked.

[0029] ii. The mediation module of the first application receives the request and uses Java's reflection mechanism to identify a method that matches the request.

[0030] iii. The meditation module of the first application allocates a reference number for the method. It then stores this number and a reference to the method in a table for future reference.

[0031] iv. The mediation module of the first application sends the reference number along with details of the types of parameters, and the return type, of the requested method.

[0032] v. The mediation module of the second application receives the reference number and the parameter types and return types.

[0033] vi. The mediation module of the second application builds a data structure describing the Java method and containing the reference number. It then returns this data structure to the second application as a remote function reference.

[0034] d. The second application makes a function call through its mediation module, providing it with the following information:

[0035] i. A reference to a function, as described above

[0036] ii. The parameters to the function call

[0037] iii. A memory address where the meditation module can store the result of the function call.

[0038] e. The second application's mediation module passes the following information to the first application's mediation module:

[0039] i. The reference number of the function

[0040] ii. The parameters to the function call

[0041] f. If, and only if, the function call is of a type that returns a result, the second application's mediation module waits for a result to be returned from the first application's mediation module before proceeding.

[0042] g. If the function call is of a type that does not return a result, the second application's mediation module has now completed its work for this function call, and returns control to the second application.

[0043] h. The first application's mediation module receives the reference number of the function and its parameters.

[0044] i. The first application's mediation module uses the reference number of the function to look up in a table a Java method reference that it has previously stored. This method is then invoked using Java's reflection mechanism.

[0045] j. If the function call is of a type that returns a result, the first application's mediation module sends the return result to the second application's mediation module.

[0046] k. The second application's mediation module returns the result of the function call to the second application.

[0047] 5. When the first application requires that the second application be notified of some event, its mediation module sends a signal on the event stream. This signal contains no information in itself.

[0048] 6. When the second application checks if any events are waiting for it, its mediation module checks the event stream to see if any notifications are waiting on it.

[0049] 7. When the second application has processed an event, its mediation module removes the event signal from the event stream.

[0050] Turning now to FIG. 3, there is shown a diagrammatic illustration of a first application using several mediation modules. A first application, for example a platform independent or interpreted application, may issue several function calls where each function is contained by a separate native code application. FIG. 3 shows a first application 100 communicating with a second application 200A through mediation modules 120A and 220A. The first application 100 may also communicate a second application 200B through mediation modules 120B and 220B.

[0051] While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.

Claims

1. A method of communicating function calls or event notification between two applications, said method comprising passing an event port number and a command port number from a first application to a second application, wherein the port numbers are stored in a memory accessible to the second application.

2. The method according to claim 1, further comprising the second application connecting a TCP/IP client socket to the event port.

3. The method according to claim 2, further comprising connecting a TCP/IP client socket to the command port.

4. The method according to claim 3, storing the connection parameters of either client socket.

5. The method according to claim 2, further comprising passing a function reference value through the command port connection.

6. The method according to claim 5, further comprising passing a function parameter through the command port connection.

7. The method according to claim 5, further comprising passing a value of memory location for storing result of a function trigger by the passing of the function reference value.

8. The method according to claim 2, further comprising passing an event notification tag through event port connection.

9. The method according to claim 8, further comprising checking the event port for an event notification tag.

10. The method according to claim 9, further comprising checking the command port in response to receiving an event notification tag.

11. The method according to claim 9, passing through the event port connection an event port notification tag relating to the completion of a function.

12. An article containing instructions and operatively connected to a processing unit, such that when said processing unit executes the instructions a first application passes to a second application an event port number and a command port number and the port numbers are stored in a memory accessible to the second application.

13. The article according to claim 12, further containing instructions that when executed by said processing unit cause the second application to connect a TCP/IP client socket to the event port.

14. The article according to claim 13, further containing instructions that when executed by said processing unit causes the second application to connect a TCP/IP client socket to the command port.

15. The article according to claim 14, further containing instructions that when executed by said processing unit cause the connection parameters of either client socket to be stored in memory.

16. The article according to claim 13, further containing instructions that when executed by said processing unit cause, the first application to pass a function reference value through the command port connection.

17. The article according to claim 16, further containing instructions that when executed by said processing unit cause the first application to pass a function parameter through the command port connection.

18. The article according to claim 16, f further containing instructions that when executed by said processing unit cause the first application to pass a value of a memory location for storing result of a function trigger by the passing of the function reference value.

19. The article according to claim 13, further containing instructions that when executed by said processing unit cause the first application to pass an event notification tag through event port connection.