Hierarchical registry structure for managing multiple versions of software components

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.

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.

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.