Technique for enabling a plurality of software components to communicate in a software component matrix environment

• US 9,203,909 B2
• Filed: 04/21/2014
• Issued: 12/01/2015
• Est. Priority Date: 08/21/2001
• Status: Expired due to Fees

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Inventors: Soukup, Martin J., Hughes, Gregory, Heffernan, Michael
• Primary Examiner(s): SHAW, PELING ANDREW
• Application Number:
  US14/257,256
• Publication Number:
  US 20140229536A1
• Time in Patent Office: 589 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A technique for enabling a plurality of software components to communicate in a software component matrix environment is disclosed. In one particular exemplary embodiment, the technique may be realized by a method for enabling a plurality of software components to communicate in a software component matrix environment comprising the steps of encoding a request at a client side; communicating the request to a server at a server side via a communication interface; comparing the request to a plurality of operations supported at the server side; determining whether a function match exists at the server side; and returning a response comprising the function match to the client side in response to the request via the communication interface wherein the response is mapped to a data model of a client.

Claims

1. A method of enabling a plurality of software components to communicate in a software component matrix environment, the method comprising, at a service locator:

automatically identifying particular services provided by particular servers to generate a service directory which associates the particular servers with the particular services provided by the particular servers;

determining an appropriate server of the particular servers for providing a specified service to a client; and

identifying the appropriate server to the client.

2. The method of claim 1, wherein the service directory also associates the particular servers with particular communication mechanisms used by the particular servers.

3. The method of claim 2, wherein the service directory also associates the particular servers with the particular communication mechanisms used by the particular servers to provide the particular services.

4. The method of claim 2, wherein the service locator is configured to download to a particular client, a particular communication mechanism when the particular communication mechanism is required by the particular client to communicate with a particular server for a particular service.

5. The method of claim 2, wherein the service locator is configured to automatically identify the particular communication mechanisms used by the particular servers to generate the service directory.

6. The method of claim 2, wherein the service locator is configured to automatically identify the particular communication mechanisms used by the particular servers to provide the particular services to generate the service directory.

7. The method of claim 1, comprising:

encoding a request for a particular service at a particular client on a client side;

communicating the request to a server side;

comparing the request to a plurality of operations supported at the server side;

determining a function match to the request at the server side; and

returning to the particular client a response comprising the function match, the response being mapped to a data model compatible with the particular client.

8. The method of claim 7, wherein determining the function match to the request at the server side comprises determining an exact function match to the request exists at the server side.

9. The method of claim 7, wherein determining the function match to the request at the server side comprises determining a closest function match to the request at the server side.

10. The method of claim 7, wherein returning to the particular client the response comprising the function match comprises filtering results of the function match based on the data model compatible with the particular client and returning the response comprising the filtered results.

11. The method of claim 7, wherein determining the function match to the request at the server side comprises:

calling a general query; and

implementing a generic interface when no function match to the request is found.

12. The method of claim 7, wherein a generic data structure abstracts an interface from the client side for inserting at least one capability into a generated application program interface object, the generated application program interface object possessing at least one of an event auto-registration function and an event auto-trigger function.

13. The method of claim 7, wherein the request is communicated from the particular client to the server side via a communication interface which comprises an iterator configured to adjust a data rate across the communication interface by sending one or more chunks of data of a preferred transfer size.

14. The method of claim 7, wherein a cache on the client side comprises a configurable persistent write through buffer allowing at least one change on one of the client side and the server side to be reflected on both the client side and the server side.

15. The method of claim 7, comprising interpreting a communication sent from a client side handler to locate one or more servers for client communication and to determine one or more communication interface types.

16. The method of claim 7, wherein the request is in extensible markup language.