System and method for on-line replacement of software

• US 6,154,878 A
• Filed: 07/21/1998
• Issued: 11/28/2000
• Est. Priority Date: 07/21/1998
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Saboff, Michael L.
• Primary Examiner(s): Chaki, Kakali
• Application Number:
  US09/120,040
• Time in Patent Office: 861 Days
• Field of Search: 395/701, 395/702, 395/703, 395/710, 395/712, 395/500.47, 395/500.48, 707/200, 707/201, 707/202, 707/203, 709/300, 709/302, 709/305, 709/310, 709/312, 709/328, 709/331, 717/1, 717/2, 717/3, 717/10, 717/11, 703/25, 703/26, 703/27
• US Class Current: 717/173
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 9/4484 Executing subprograms
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A system for changing a software library during the execution of a software application using the software library. The software application interfaces to the software library only through the use of an interface library, to ensure that the software application does not directly bind with the software library. With no direct binding the software library can be updated during runtime without the software application re-resolving the location of the software library. The update is triggered by a change of the version number in a registry. The program correctness is maintained by library management services ensuring that the software library is no longer in use by the application before updating to the new library. Memory management services are used to ensure that the state of the library is maintained between the old and the updated versions of the software library.

Claims

1. A shared library system embodied in a computer to support dynamic on-line replacement of a shared software library in the computer while preserving application program compatibility, the system comprising:

an implementation library including at least one routine, the implementation library being loadable, the implementation library providing a service;

an interface library including at least one proxy interface to each routine in the implementation library, the proxy interface being linkable to an application program for accessing the corresponding routine; and

a service registry including at least one entry for mapping the interface library to its corresponding implementation library, so that the implementation library can be modified while the system is executing the application program.

2. A system according to claim 1, wherein the interface library further includes global data, so that the application program and the implementation program can, in common, access the global data of a routine in the implementation library, without providing for relocation of the global data following modification of the implementation library.

3. A system according to claim 1, wherein the service registry is stored in a file that is accessible to the interface library, the interface library determining when the implementation library has been modified.

4. A system according to claim 1 further comprising a software means for maintaining the service registry so as to indicate that an implementation library updated request is pending.

5. A system according to claim 1 wherein each entry in the registry includes an indication of the service provided by the implementation library, a version for the implementation library and an indication of the location of the implementation library.

6. A system according to claim 1, further comprising a software means for managing the loading and unloading of implementation libraries while maintaining program correctness.

7. A system according to claim 1, wherein:

the implementation library includes one or more state variables, each state variable having a respective value, and the values of the state variables together defining a state of the implementation library; and

the shared library system further includes a software means for managing the memory allocation of the implementation library so that the state of the implementation library can be restored upon update of the implementation library.

8. A system according to claim 1 further comprising a pointer linkage table, comprising at least one pointer entry, the pointer entry, the pointer entry pointing to the proxy interface library if the implementation library is being modified, otherwise the pointer entry pointing to the implementation library.

9. A method of implementing on-the-fly replacement of an implementation library so as to allow updating the implementation library while maintaining correct operation of an application that uses a software routine within the implementation library, the replacement method comprising the steps of:

providing a first version of the implementation library;

establishing an interface library corresponding to the implementation library, the interface library including a proxy routine for the software routine within the implementation library;

linking the interface library to the application that uses the software routine within the implementation library;

executing a call in the application to the software routine within the implementation library;

responsive to the call to the software routine, transferring control to the corresponding proxy interface in the interface library;

determining whether the implementation library is marked for updating, and if it is, replacing the first version of the implementation library with a second version of the implementation library;

transferring control to the corresponding software routine in the implementation library;

executing the corresponding software routine in the implementation library;

returning control to the application at a return point immediately following executed call; and

continuing executing of the application beginning at the said return point.

10. A method according to claim 9, where the step of returning control to the application is preceded by the step of returning control to the proxy interface in the interface library.

11. A method according to claim 9, wherein the step of linking the interface library to the application is performed by statically linking the interface library to the application.

12. A method according to claim 9, wherein the step of linking the interface library to the application is performed by dynamically linking the interface library to the application.

13. A method according to claim 9, the software routine in the implementation library having a location, further including the steps of:

providing a registry entry associated with the implementation library, the registry entry including an indication of a service provided by the implementation library, a version of the implementation library and a location of the implementation library;

prior to the step of executing the call in the application to the software routine with in the implementation library, identifying a last used version of the implementation library; and

comparing the identified last used version of the implementation library to the version indicated in the registry entry to determine whether the implementation library has been updated.

14. A method according to claim 13, wherein the step of transferring control to the corresponding software routine in the implementation library includes:

determining the location of the software routine in the implementation library based on the location for the implementation library currently in the registry entry; and

branching to the said determined location.

15. A method according to claim 13, wherein:

the registry entry further including a rule controlling access to the implementation library;

the step of comparing the identified last used version of the implementation library to the version indicated in the registry entry includes using the rule in the registry entry to determine whether or not to use the updated implementation library; and

the step of determining whether the implementation library is marked for updating includes;

if the rule in the registry entry is satisfied, replacing the first version of the implementation library with the second version of the implementation library; and

if the rule in the registry entry is not satisfied, retaining the first version of the implementation library.

16. A method according to claim 9, wherein the implementation library further comprises one or more state variables, each state variable having a respective value, and the values of the state variables together defining a state of the implementation library, the step of replacing the implementation library comprising the steps of:

unloading the implementation library provided in the first version, so that the implementation library provided in the first version is no longer available to the application;

loading the implementation library provided in the second version, so that the implementation library provided in the second version is available to the application; and

restoring the state of the implementation library provided in the second version so that it matches the state of the implementation library provided in the first version.

17. A method according to claim 9, wherein prior to the step of transferring control to the proxy interface, performing the steps of:

obtaining a branch location from a pointer linkage table; and

if the branch location indicates the proxy interface library proceeding with the step of transferring control to the corresponding proxy interface, otherwise proceeding to the step of transferring control to the corresponding software routine.

18. An on-the-fly replaceable implementation library for use in a replaceable software system embodied in a computer, the implementation library comprising:

one or more software routines for implementing a selected service;

an interface for use by an external software component using the selected service, the interface allowing for a call from the external software component but not allowing for a binding to the external software component;

one or more state variables, each state variable having a respective value, the values of the state variables together defining a library state; and

a means for restoring the library state to match a library state of a previous version of the implementation library.

19. A proxy interface library for use in a replaceable software system embodied in a computer, the proxy interface library being associated with a corresponding implementation library and comprising:

a proxy interface corresponding to a routine within the corresponding implementation library;

the proxy interface being linkable to an application as a proxy for the corresponding routine in the implementation library;

means for locating the corresponding routine in the implementation library; and

means for transferring execution control to the corresponding routine in the implementation library in response to execution of a call in an application to the corresponding routine in the implementation library, whereby the proxy interface library is transparent to the application.

20. A proxy interface library according to claim 19 and further comprising a call-back loop for detecting a request to update the corresponding implementation library during execution of a routine within the corresponding implementation library.

21. A pointer linkage table stored in a machine readable medium for directing an application running on a computer to either a proxy interface library or an implementation library, the pointer linkage table comprising at least one pointer entry, each pointer entry pointing to the proxy interface library so that the application, in accordance with the pointer linkage table, calls the implementation library unless the implementation library is being updated, in which case the application calls the proxy interface library if the implementation library is being modified, otherwise the pointer entry pointing to the implementation library.