Automatic feature augmentation for component based application programming interfaces

• US 20020083212A1
• Filed: 12/22/2000
• Published: 06/27/2002
• Est. Priority Date: 12/22/2000
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Salmon, Glen E.
• Granted Patent: US 6,848,110 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading

Abstract

Automatically augmenting functionality in an application programming interface (“API”) is provided by receiving from an application a request for functionality to be fulfilled by a first component implementing at least a portion of the functionality within the application programming interface. The first component is queried for the requested functionality. If an indication that the first component does not implement the requested functionality is received, the a search for an augmentation component that implements the requested functionality is initiated. If an augmentation component supplying the required functionality is found, the augmentation component is loaded to fulfill the request for functionality in place of the first component and used to respond to the request for functionality. Augmentation components provide a subset of the API'"'"'s required functionality, thereby removing a limitation from API components (i.e., functionality completeness). Augmentation components may also be used to provide new functionality for the API to all existing components (i.e., functionality enhancement).

Claims

1. A method of automatically augmenting functionality in an application programming interface comprising the steps of:

receiving from an application a request for functionality to be fulfilled by a first component implementing at least a portion of the functionality within the application programming interface;

querying the first component for the requested functionality;

receiving an indication from the first component that the requested functionality is not implemented by the first component;

searching for an augmentation component that implements the requested functionality;

loading the augmentation component to fulfill the request for functionality in place of the first component; and

responding to the request for functionality using the loaded augmentation component.

2. The method of claim 1 wherein the searching step comprises looking for the augmentation component on a computer system executing the application.

3. The method of claim 1 wherein the searching step comprises looking for the augmentation component on a network connected to a computer system executing the application.

4. The method of claim 3 wherein the network uses a Uniform Resource Locator to address resources and the searching step uses the Uniform Resource Locator to direct the search.

5. The method of claim 1 wherein the querying, receiving and searching steps create and maintain a catalog of available augmentation component functionality, the catalog being used to determine whether an augmentation component that implements the requested functionality exists.

6. The method of claim 5 wherein the catalog is created upon the first request for functionality.

7. The method of claim 5 wherein the catalog is recreated upon a specific request.

8. The method of claim 1 wherein the first component is a connector for accessing information stored in databases, file systems, Enterprise Resource Planning systems or transaction systems.

9. An apparatus for automatically augmenting functionality in an application programming interface comprising:

an application programming interface module receiving from an application a request for functionality to be fulfilled by a first component implementing at least a portion of the functionality within the application programming interface;

a query unit within the application programming interface module querying the first component for the requested functionality;

a receiver within the application programming interface module receiving an indication from the first component that the requested functionality is not implemented by the first component;

a search unit within the application programming interface module searching for an augmentation component that implements the requested functionality;

a loader within the application programming interface module loading the augmentation component to fulfill the request for functionality in place of the first component; and

a response unit within the application programming interface module responding to the request for functionality using the loaded augmentation component.

10. The apparatus of claim 9 wherein the search unit comprises looking for the augmentation component on a computer system executing the application.

11. The apparatus of claim 9 wherein the search unit comprises looking for the augmentation component on a network connected to a computer system executing the application.

12. The apparatus of claim 11 wherein the network uses a Uniform Resource Locator to address resources and the searching unit uses the Uniform Resource Locator to direct the search.

13. The apparatus of claim 9 wherein the receiver, the query unit, and the search unit create and maintain a catalog of available augmentation component functionality, the catalog being used to determine whether an augmentation component that implements the requested functionality exists.

14. The apparatus of claim 13 wherein the catalog is created upon the first request for functionality.

15. The apparatus of claim 13 wherein the catalog is recreated upon a specific request.

16. The apparatus of claim 9 wherein the first component is a connector for accessing information stored in databases, file systems, Enterprise Resource Planning systems or transaction systems.

17. An apparatus for automatically augmenting functionality in an application programming interface comprising:

a means for receiving from an application a request for functionality to be fulfilled by a first component implementing at least a portion of the functionality within the application programming interface;

a means for querying the first component for the requested functionality;

a means for receiving an indication from the first component that the requested functionality is not implemented by the first component;

a means for searching for an augmentation component that implements the requested functionality;

a means for loading the augmentation component to fulfill the request for functionality in place of the first component; and

a means for responding to the request for functionality using the loaded augmentation component.

18. A computer program product comprising:

a computer usable medium for automatically augmenting functionality in an application programming interface;

a set of computer program instructions embodied on the computer usable medium, including instructions to;

receive from an application a request for functionality to be fulfilled by a first component implementing at least a portion of the functionality within the application programming interface;

query the first component for the requested functionality;

receive an indication from the first component that the requested functionality is not implemented by the first component;

search for an augmentation component that implements the requested functionality;

load the augmentation component to fulfill the request for functionality in place of the first component; and

respond to the request for functionality using the loaded augmentation component.

19. A computer data signal embodied in a carrier wave comprising a code segment for automatically augmenting functionality in an application programming interface, including instructions to:

receive from an application a request for functionality to be fulfilled by a first component implementing at least a portion of the functionality within the application programming interface;

query the first component for the requested functionality;

receive an indication from the first component that the requested functionality is not implemented by the first component;

search for an augmentation component that implements the requested functionality;

load the augmentation component to fulfill the request for functionality in place of the first component; and

respond to the request for functionality using the loaded augmentation component.