Hierarchical registry structure for managing multiple versions of software components

• US 6,185,734 B1
• Filed: 07/21/1998
• Issued: 02/06/2001
• 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: Maag, Andrew, Saboff, Michael L., McGowen, Alan
• Primary Examiner(s): Chaki, Kakali
• Application Number:
  US09/120,037
• Time in Patent Office: 931 Days
• Field of Search: 707/200-203, 707/100, 717/10, 717/11
• US Class Current: 717/164
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

The invention describes a hierarchical registry for allowing multiple applications to use different versions of a software component on the same system. Each version of a software component has a base entry in the registry. Each base entry has rules, one of which must be met to use version of the software component corresponding to that base entry. The registry may also have a default base entry, which is used if no other base entry has one of its rules met. Each rule may have several criteria, all of which must be met to satisfy that rule. Each base entry may be marked as deleted rendering the corresponding version of the software component inaccessible except by applications currently accessing the version marked as deleted.

Claims

1. A software registry data structure stored in a machine readable medium for managing multiple versions of a software service used by an application running on a computer, the registry data structure comprising:

one or more base entries each indicating a version of the software service, each base entry including one or more rules, of which at least one rule of a base entry must be satisfied to use the corresponding version of the software service indicated by the base entry, so that the application utilizes the version of the software service corresponding to the base entry with the satisfied rule.

2. A software registry data structure according to claim 1, further including a default base entry, indicating a default version of the software service, wherein if all base entries fail to satisfy any of its rules then the default version of the software service is used.

3. A software registry data structure according to claim 1, whereby each rule for a base entry comprises one or more criteria, whereby each criterion of a rule must be met to satisfy the rule.

4. A software registry data structure according to claim 3, wherein all of the criteria for a rule are connected in a linked list.

5. A software registry data structure according to claim 1, whereby each version of the software service comprises a software library.

6. A software registry data structure according to claim 1, whereby each version of the software service comprises a software program.

7. A software registry data structure according to claim 1, whereby each version of the software service comprises a software procedure.

8. A software registry data structure according to claim 1, whereby each base entry:

an indication of the software service provided by the base entry;

a version indicator corresponding to a version of the software service; and

a memory location corresponding to a version of the software service.

9. A software registry data structure according to claim 8, whereby each base entry further comprises:

a dependency, indicating a dependent software component, used by the corresponding version of the software service.

10. A software registry data structure according to claim 8, whereby each base entry further comprises:

a prerequisite, indicating an earlier version of the software service, needed to construct the corresponding version of the software service.

11. A software registry data structure according to claim 8, whereby each base entry further comprises:

a list of extensions, each extension indicating an additional software component providing an additional capability of the software service.

12. A software registry data structure according to claim 1, wherein all base entries are connected so as to form a linked list.

13. A software registry data structure according to claim 1, wherein all rules for a base entry are connected in a linked list.

14. A software system for managing multiple versions of a software service, the system comprising:

a digital computer with memory;

a software service available in a multiple versions, each version existing in the memory;

a software registry existing in the memory, the registry comprising one or more base entries, each base entry having at least one rule and each base entry corresponding to a version of the software service; and

a software application existing in the memory and constructed and arranged to match at least one of the rules of a base entry and therefore using the version of the software service corresponding to the matching base entry.

15. A system according to claim 14, wherein the registry further comprises a default base entry corresponding to a default version of the software service, the software application constructed and arranged not to match any of the rules of any of the base entries and therefore use the default version of the software service.

16. A system according to claim 14, each rule of each base entry comprising at least one criterion, the software application constructed and arranged to meet all of the criterion of at least one rule of a base entry and therefore use the corresponding version of the software service.

17. A system according to claim 16, wherein the registry further comprises a default base entry corresponding to a default version of the software service;

the software application constructed and arranged such not to match all of the criterion of any of the rules of any of the base entries and therefore use the default version of the software service.

18. A system according to claim 14, wherein each version of the software service comprises a software library.

19. A system according to claim 14, wherein each version of the software service comprises a software procedure.

20. A system according to claim 14, wherein each version of the software service comprises a software program.

21. A method for selecting a version of a software service for use by a software application using a registry, the registry comprising one or more base entries each corresponding to a version of the software service, each base entry comprising one or more rules, the method comprising the steps:

for each base entry

testing each rule of the base entry;

selecting the version of the software service corresponding to the base entry if any rule of the base entry is satisfied.

22. A method according to claim 21, wherein the registry further comprises a default base entry corresponding to a default version of the software service, the method further comprising the step:

selecting the default version of the software service, if no rule of any base entry is satisfied.

23. A method according to step 21, each rule of each base entry comprises one or more criteria, whereby the step of testing each rule of the base entry comprises the steps of:

testing all criteria of the rule;

if all criteria are satisfied, satisfying the rule, otherwise not satisfying the rule.

24. A method for deleting a version of a software service using a registry, the software service available in a first version and a second version, the registry comprising a first base entry and a second base entry, each base entry comprising a state, the method comprising the steps of:

marking the state of the first base entry corresponding to the first version of the software service as deleted;

redirecting an original access to the first version of the software service to the second version of the software service because the first base entry has a state of deleted; and

allowing an on-going access to the first version of the software service to allow a user of the software service to finish its use of the first version of the software service even though the first base entry has a state of deleted.

25. A software registry data structure stored in a machine readable medium for use in a replaceable software system by an application running on a computer, the data structure comprising:

a series of entries, each entry associated with a respective software library, and at least one of the entries comprising;

a first element for storing an identification of the corresponding software library;

a second element for storing an indication of a current version of the corresponding software library;

a third element for storing a location of the corresponding software library; and

a fourth element for storing one or more rules controlling the use of the corresponding software library,

so that the application uses the current version of the corresponding software library when the rules controlling the use of the corresponding software library are satisfied.

26. A software registry data structure according to claim 25 wherein the said entry further includes an indication of a pending request to update the corresponding software library.

27. A software registry data structure according to claim 25 wherein the said entry further includes an indication that the corresponding software library has been updated.

28. A software registry data structure according to claim 25 wherein a second of the entries comprises the first, second, and third elements, the second of the entries having no rules controlling the use of the corresponding software library.