Method and apparatus for determining at execution compatibility among client and provider components where provider version linked with client may differ from provider version available at execution

• US 5,613,101 A
• Filed: 06/07/1995
• Issued: 03/18/1997
• Est. Priority Date: 05/05/1993
• Status: Expired due to Term

• Current Assignee: Apple Computer Incorporated (Apple Inc.)
• Original Assignee: Apple Computer Incorporated (Apple Inc.)
• Inventors: Lillich, Alan W.
• Primary Examiner(s): Kim, Ken S.
• Application Number:
  US08/483,621
• Time in Patent Office: 650 Days
• Field of Search: 395/500, 395/700
• US Class Current: 709/230
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• 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

Abstract

The invention is a method and apparatus for verifying compatibility between components of a system which share a client-provider relationship. Briefly, according to the invention, a current version of a provider and a compatibility range are defined for each of a version of a client and a version of a provider. A version of a provider specifies an oldest implementation provider and an oldest definition provider. When a client is linked with a particular version of a provider it stores an identification for that provider, a current indicator for that version of the provider, called a definition provider, and the oldest implementation provider. At runtime, compatibility checks are performed between a client and available versions of the provider(s), called implementation providers, with which it has been linked. For each available version of each type of provider compatibility exists with the client in three situations. First, if the definition provider and the implementation provider are the same version of that provider, then the client and provider are compatible. Second, if the definition provider, i.e. the version of the provider linked with the client, is newer than the implementation provider, then if the version of the implementation provider is no older than the oldest implementation provider specified in the client, the two are compatible, otherwise they are incompatible. Third, if the definition provider is older than the implementation provider, then if the definition provider is no older than the oldest definition provider specified in the implementation provider, then the two are compatible.

Claims

1. A method for verifying compatibility between modular components in a system having a processor, at least one client component and at least one provider component, the at least one provider component capable of providing services to the at least one client component, a provider component having one or more versions, the at least one client being linked to a version of a provider component during the creation of an executable file of the at least one client and the at least one client, during execution on the processor, using a version of the provider component which is available in the system at the time of execution, wherein the provider component used during execution may be a different version than the provider component to which the client was linked, said method comprising the steps of:

specifying a provider indicator for each provider component, said provider indicator identifying a provider component'"'"'s type and uniquely identifying the provider component in a manner that distinguishes the provider component from other provider components;

specifying a current indicator for each version of each provider component, said current indicator having a value identifying a version of the provider component in a manner which distinguishes the version from other versions of the provider component;

specifying for each version of each provider component a compatibility range, the compatibility range for a version of a provider component identifying a range of versions of the provider component which are compatible with that version of the provider component such that during execution of a client that version of the provider can be used as long as the client was built using a version of the provider component identified in that version'"'"'s compatibility range;

specifying for each client component a compatibility range for each provider component to which it is linked, each compatibility range identifying a range of versions of a provider component which can be used to execute the client component;

linking the at least one client to a provider component to construct an executable client component;

associating the at least one client with the current indicator of the linked provider component;

when a client component is executed, determining which of the at least one provider component and versions thereof are available on the system and connecting the client component and the available at least one provider component such that information such as the current indicator and compatibility range of the provider component, the current indicator of a provider component associated with the client component during linking, and the compatibility range of the client can be exchanged between the connected client component and the available at least one provider component;

determining compatibility between the client component and the connected at least one provider component, the determination being based on the current indicator of the at least one provider component, the current indicator of a provider component associated with the client component during linking, and the compatibility range of the newer of the at least one provider component and the client component such that compatibility is found to exist when the current indicator of the at least one provider component and the current indicator of the linked provider component indicate substantially the same version of the provider component or when the current indicator of the older of the at least one provider component and the linked provider component is within the compatibility range of the newer of the at least one provider component and the client component; and

indicating whether compatibility exists.

2. A method defined in claim 1 wherein the steps of determining compatibility and indicating whether compatibility exists includes the steps of:

comparing the value of the current indicator of the connected provider component to the value of the current indicator associated with the client component during linking and if the two values indicate substantially the same versions, then indicating compatibility,

and if the two versions are not substantially the same, then if the value of the current indicator associated with the client component indicates a version which is newer than the version indicated by the value of the current indicator of the provider component, then if the version specified by the value of the current indicator of the provider component is within the compatibility range of the client component, then indicating compatibility, otherwise indicating incompatibility,

and if the value of the current indicator of the provider component indicates a version which is newer than the version indicated by the value of the current indicator stored in the client component, then if the version specified by the value of the current indicator associated with the client component is within the compatibility range of the connected provider component, indicating compatibility, otherwise indicating incompatibility.

3. A method as defined in claim 2 wherein the current indicator of a version of a provider component is defined such that its value is greater than or equal to the values of current indicators of prior versions of that provider component and a version indicated by a value of a first current indicator is newer than a version indicated by a value of a second current indicator when the value of the first current indicator is greater than the value of the second current indicator.

4. A method as defined in claim 1 wherein the compatibility range specified for a particular version of a provider component indicates an oldest version of the provider component capable of building a client component which which can be used to execute the particular version of the provider.

5. A method as defined in claim 1 wherein the compatibility range specified for a particular client component which is linked to a particular provider component indicates an oldest version of the particular provider component which can be used to execute the particular client component.

6. A method for verifying compatibility between modular components in a system having a processor, at least one client component and at least one provider component, a provider component having one or more versions, the at least one provider component capable of providing services to the at least one client component, the at least one client being linked to a version of a provider component during the creation of an executable file of the at least one client and the at least one client, during execution on the processor, using a version of the provider component which is available in the system at the time of execution, wherein the provider component used during execution may be a different version than the provider component to which the client was linked, the linked provider component supplying definitions of an application interface to the client component, said provider component capable of supplying definitions, implementation or both, said method comprising the steps of:

specifying a provider indicator for each provider component, said provider indicator identifying a provider component'"'"'s type and uniquely identifying the provider component in a manner that distinguishes the provider component from other provider components;

specifying a current indicator for each version of a provider component, said current indicator having a value identifying a version of the provider component in a manner which distinguishes the version from other versions of the provider component;

specifying for each version of a provider component an oldest implementation indicator, the oldest implementation indicator indicating an oldest version of that provider component having an implementation which is compatible with definitions supplied by the each version of the provider component;

specifying for each version of a provider an oldest definition indicator, the oldest definition indicator indicating an oldest version of that provider component which supplies definitions that are compatible with the implementation of the each version of the provider component;

when a client component is being linked with a version of a provider component, associating with the client component the provider indicator, the current indicator and the oldest implementation indicator of that version of the provider component being linked;

when a client component is executed, determining which of the at least one provider component and versions thereof are available on the system and connecting the client component and the available at least one provider component such that information such as the provider indicator, the current indicator of the connected provider component, the current indicator of a provider component associated with the client component during linking, oldest implementation indicator and oldest definition indicator can be exchanged between the connected client component and the available at least one provider component;

determining compatibility between the client component and the connected at least one provider component, the determination being based on the values of the provider indicator, the current indicator of the connected provider component, the current indicator of a provider component associated with the client component during linking, the oldest implementation indicator and the oldest definition indicator, the determination further being based on the newer of the versions indicated by the current indicator of the connected provider component and the current indicator of the associated provider component; and

indicating whether compatibility exists.

7. A method defined in claim 6 wherein the steps of determining compatibility and indicating whether compatibility exists includes the steps of:

comparing the value of the current indicator of the connected provider component to the value of the current associated with the client component and if the two values indicate substantially the same version, then indicating compatibility,

and if the two versions are not substantially the same, then if the value of the current indicator associated with the client indicates a version which is more recent than the version indicated by the value of the current indicator of the connected provider component, then if the oldest implementation indicator associated with the client component specifies a version which is older or the same as the version indicated by the value of the current indicator of the provider, then indicating compatibility, otherwise indicating incompatibility,

and if the value of the current indicator of the provider component indicates a version which is more recent than the version indicated by the value of the current indicator associated with the client component, then if the version specified by the value of the oldest implementation indicator of the provider component is older than or the same as the version indicated by the value of the current indicator associated the client, then indicating compatibility, otherwise indicating incompatibility.

8. A method defined in claim 6 wherein the steps of determining compatibility and indicating whether compatibility exists includes the steps of:

comparing the value of the current indicator of the connected provider component to the value of the current indicator associated with the client and if the two values indicate substantially the same version, then indicating compatibility,

and if the two versions are not substantially the same, then if the absolute value of the value of the current indicator associated with the client component is greater than the absolute value of the value of the current indicator of the connected provider component, then if the absolute value of the value specified by the oldest implementation indicator associated with the client component is less than or equal to the absolute value of the value of the current indicator of the provider component, then indicating compatibility, otherwise indicating incompatibility,

and if the absolute value of the value of the current indicator of the provider component is greater than the absolute value of the value of the current indicator associated with the client, then if the absolute value of the value specified by the oldest definition implementation of the provider component is less than or equal to the absolute value of the value of the current indicator associated with the client component, then indicating compatibility, otherwise indicating incompatibility.

9. A method defined in claim 6 wherein the steps of determining compatibility and indicating whether compatibility exists includes the steps of:

forming a list of available versions of one or more provider components, the list having an element for each version of a provider component, each element specifying the provider indicator, the current indicator and the oldest definition implementation for the version of the provider component specified by the element;

initializing a compatibility indicator which specifies a best compatible version, if any exists, among the versions specified by version indicators in elements in the list;

searching fields of the list for a best compatible version of the provider component by determining for each element compatibility between a version of the provider component specified by the current indicator of that element and the client component and, if compatible, comparing the version specified by the current indicator of the element to a version specified by the compatibility indicator to determine which is better and if the version specified by the version indicator of the element is better, then setting the compatibility indicator to indicate the version specified by the current indicator; and

indicating whether a compatible version is found and, if so, indicating which version is the best compatible version.

10. A method defined in claim 9 wherein compatibility between the version specified by the current indicator of the element and the version specified by the current indicator associated with the client component is determined and indicated by comparing the version specified by the current indicator of the element and the version specified by the current indicator associated with the client and if the two versions are substantially the same, then indicating compatibility,

and if the two versions are not substantially the same and if the value of the current indicator associated with the client component specifies a version which is newer than the version specified by the value of the current indicator of the element then if the oldest implementation indicator associated with the client component specifies a version which is older than or the same as the version specified by the current indicator of the element, then indicating compatibility, otherwise indicating incompatibility,

and if the version specified by the value of the current indicator of the element is newer than the version specified by the value of the current indicator associated with the client component, then if the version specified by the oldest definition indicator of the provider component is older than or the same as the current indicator associated with the client component, then indicating compatibility, otherwise indicating incompatibility.

11. A method defined in claim 9 wherein a first version of a provider component is better than a second version of a provider component if the first version is newer than the second version.

12. A method defined in claim 9 wherein a first version is newer than a second version if a first value specifying the first version is greater than a second value specifying the second version.

13. A method defined in claim 9 wherein a best compatible version is the compatible version specified by a value which is numerically closest to the value specified by the current indicator associated with the client component and if two compatible versions have substantially the same numerical closeness to the value specified by the current indicator associated with the client component and those two compatible versions are the numerically closest to the value specified by the current indicator associated with the client component, then the newer of the two versions is the best compatible version.

14. A method defined in claim 9 wherein a best compatible version is the compatible version which is numerically closest to the value specified by the current indicator associated with the client component and which is more recent or equal in age to the version specified by the value of the current indicator associated with the client.

15. An apparatus for verifying compatibility between components in a system having a processor, at least one client component and at least one provider component which supplies definitions of an application interface to the client component, said apparatus comprising:

a memory;

a disk drive;

one or more client components stored on said disk drive;

one or more provider components, each provider component being stored on said disk drive, each of said provider components having one or more versions;

a linker for linking a client component to one or more provider components to create an executable file of the at least one client, said linker stored on said disk drive;

a processor capable of loading into memory and executing a linker, one or more client components and one or more provider components;

means for specifying a provider indicator for each provider component, said provider indicator identifying a provider component'"'"'s type and uniquely identifying the provider component in a manner which distinguishes the provider component from other provider components, said provider indicator being associated with a client component when the client component is linked to the provider component;

means for specifying a current indicator for each version of each provider, said current indicator having a value identifying a version of the provider component in a manner which distinguishes the version from other versions of the provider component, said current indicator being associated with a client component when the client component is linked to the provider component;

means for specifying a compatibility range for each version of each provider component and for each client component linked with that provider component, said compatibility range being associated with a client component when the client component is linked to the provider component;

a connector for determining at execution of a client component available provider components and for connecting a client component to one or more available provider components such that information such as the provider indicator, current indicator and compatibility ranges can be exchanged between the connected client component and the available at least one provider component;

means for determining compatibility based on the values of the current indicator of the connected provider component, the current indicator associated with the client component and the compatibility ranges of the provider and client components, compatibility existing when the current indicator of the associated provider component and the current indicator of the connected provider component indicate substantially the same version or when the older of the versions specified by the current indicator of the associated provider component and the current indicator of the connected provider component is within the compatibility range of the newer of said versions; and

means for indicating compatibility.

16. A method for defining compatibility between components in a system having a processor, at least one client component and at least one provider component, a provider component having one or more versions, the at least one provider component capable of providing services to the at least one client component, said method comprising the steps of:

specifying a provider indicator for each provider component, said provider indicator identifying a provider component'"'"'s type and uniquely identifying the provider component in a manner that allows the provider component to be distinguished from other provider components;

specifying a current indicator for each version of each provider, said current indicator having a value identifying a version of the provider component in a manner which distinguishes it from other versions of the provider component; and

specifying compatibility ranges for each version of each provider component, a compatibility range for a particular version identifying a range of versions of the provider component which are compatible and interoperable with the particular version,

wherein said current indicator and compatibility ranges are defined such that compatibility exists between a first and second version of a provider component, said first version of the provider component being linked to the client component and said second version of the provider component being available at execution of the client component on a processor when (A) the current indicator of the first version of the provider component and the current indicator of the second version of the provider indicate substantially the same version of the provider component, or when (B) the current indicator of the second version of the provider component indicates a newer version than the current indicator of the first version of the provider component and the first version of the provider component is within the compatibility range of the second version of the provider component, or when (C) the current indicator of the first version of the provider component indicates a newer version than the current indicator of the second version of the provider component and the second version of the provider component is within the compatibility range of the first version of the provider component.

17. A method for defining compatibility between components in a system having at least one client component and at least one provider component, each provider component having one or more versions, said client component being linked to a version of a provider component which supplies definitions of an application interface to the client component and executing with a version of a provider component which may be the same or different than the version of the provider component that supplied the definitions to the client component during linking, said method comprising the steps of:

specifying a provider indicator for each provider component, said provider indicator identifying a provider component'"'"'s type and uniquely identifying the provider component in a manner that allows the provider component to be distinguished from other provider components;

specifying a current indicator for each version of each provider, said current indicator having a value identifying a version of the provider component in a manner which distinguishes it from other versions of the provider component;

specifying an oldest implementation indicator for each version of each provider, the oldest implementation indicator indicating an oldest version of that provider component having an implementation which is compatible with definitions supplied by the each version of the provider component; and

specifying for each version of a provider an oldest definition indicator, the oldest definition indicator indicating an oldest version of that provider component which supplies definitions that are compatible with the implementation of the each version of the provider component,

wherein said current indicator and compatibility ranges are defined such that compatibility exists between a first and second version of a provider component, said first version of the provider component being linked to the client component and said second version of the provider component being available at execution of the client component on a processor when (A) the current indicator of the first version of the provider component and the current indicator of the second version of the provider indicate substantially the same version of the provider component, or when (B) the current indicator of the second version of the provider component indicates a newer version than the current indicator of the first version of the provider component and the current indicator of the first provider component indicates a version that is no older than the version specified by the oldest definition indicator of the second version of the provider component or when (C) the current indicator of the first version of the provider component indicates a newer version than the current indicator of the second version of the provider component and the current indicator of the second version of the provider component indicates a version that is no older than the version specified by the oldest implementation indicator of the first version of the provider component.

18. A method as defined in claim 17, said method further comprising the steps of:

linking a client component with a version of a provider component; and

associating with the client program the provider indicator, current indicator and oldest implementation indicator of the version of the provider being linked with the client component.

19. An apparatus for verifying compatibility between components in a system having a processor, at least one client component and at least one provider component which supplies definitions of an application interface to the client component, the at least one provider component capable of providing services to the at least one client component, said apparatus comprising:

a first computer system having a processor and a storage unit;

a second computer system having a processor and a storage unit;

a linker stored in said storage unit of said first computer system for linking a client component to one or more provider components, said linking creating an executable file of said client component;

one or more client components stored in one of said storage units;

one or more provider components, each provider component being stored on said disk drive, each of said provider components having one or more versions;

means for specifying a provider indicator for each provider component, said provider indicator identifying a provider component'"'"'s type and uniquely identifying the provider component in a manner which distinguishes the provider component from other provider components, said provider indicator being associated with a client component when the client component is linked to the provider component;

means for specifying a current indicator for each version of each provider, said current indicator having a value identifying a version of the provider component in a manner which distinguishes the version from other versions of the provider component, said current indicator being associated with a client component when the client component is linked to the provider component;

means for specifying a compatibility range for each version of each provider component and for each client component linked with that provider component, said compatibility range being associated with a client component when the client component is linked to the provider component;

a connector for determining at execution of a client component available provider components and for connecting a client component to one or more available provider components such that information such as the provider indicator, current indicator and compatibility ranges can be exchanged between said connected client component and said one or more available provider components, said connector being on each of said first and second computer systems such that said client component can be executed on either said first or said second computer system;

means for determining compatibility based on the values of the current indicator of the connected provider component, the current indicator associated with the client component and the compatibility range of the newer of the at least one provider component and the client component such that compatibility is found to exist when the current indicator of the at least one provider component and the current indicator of the linked provider component indicate substantially the same version of the provider component or when the current indicator of the older of the at least one provider component and the linked provider component is within the compatibility range of the newer of the at least one provider component and the linked provider component; and

means for indicating compatibility.