Generating unique name/version number pairs when names can be re-used

• US 7,546,322 B2
• Filed: 03/09/2005
• Issued: 06/09/2009
• Est. Priority Date: 03/09/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Lehner, Mary Claire
• Primary Examiner(s): Lu; Kuen S
• Assistant Examiner(s): Owyang; Michelle
• Application Number:
  US11/076,653
• Publication Number:
  US 20060206540A1
• Time in Patent Office: 1,553 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

Various embodiments of a method, system and article of manufacture provide a version number. An object has a present name and a present version number. In response to changing the present name of the object to a different name, the different name having been used by one or more other objects, one or more values of one or more first components of one or more other version numbers associated with the one or more other objects, respectively, are identified. An other version number is generated wherein a value of the first component of the other version number is different from the one or more values of the one or more first components.

Claims

1. A computer-implemented method of providing a version number of a first versioned object having a present name and a present version number, comprising:

in response to changing said present name of said first versioned object to a different name, said different name having been used by a second versioned object, said first versioned object being a first file, said present name being a file name of said first file, said second versioned object being a second file, said second file being different from said first file, said different name being a file name of said second file, said different name not being used by a previous version of said first versioned object, said second versioned object using said different name being associated with an existing version number comprising delimiter-separated components having a starting component and an ending component, said starting component being a left-most component of said delimiter-separated components, said ending component being a right-most component of said delimiter-separated components,

identifying a value of said starting component of said existing version number associated with said second versioned object;

generating a new version number for said first versioned object having said different name, said new version number comprising a new plurality of components, wherein a value of a new starting component of said new plurality of components of said new version number is different from said value of said starting component of said existing version number associated with said second versioned object, said new starting component being a left-most component of said new plurality of components of said new version number;

wherein in response to said different name being associated with a first successor of said first versioned object with respect to said present version number, said generating increments a value of an ending component of said present version number to provide a new ending component of said new plurality of components of said new version number, said new ending component being a right-most component of said new plurality of components; and

wherein in response to said different name being associated with an n^th successor of said first versioned object with respect to said present version number, where n is greater than one, said generating said new version number appends a component pair comprising a pair component equal to n−

1 and another pair component equal to a predetermined value to a right end of said new version number.

2. The method of claim 1 wherein a third versioned object having another existing version number uses said different name, said another existing version number comprising another delimiter-separated components having another starting component and another ending component, wherein said identifying identifies a highest value of said starting component of said existing version number associated with said second versioned object and said another starting component of said another existing version number associated with said third versioned object, and said generating said new version number comprises incrementing said highest value by a predetermined value to provide an incremented value, and said new starting component of said new plurality of components of said new version number is set to said incremented value.

3. The method of claim 1 wherein said new plurality of components of said new version number is a delimiter-separated series of components.

4. The method of claim 1 wherein a uniform resource identifier (URI) comprises said different name and said new version number.

5. The method of claim 4 further comprising:

displaying said first versioned object associated with said URI.

6. An article of manufacture for providing a version number of a first versioned object having a present name and a present version number, said article of manufacture comprising:

a computer readable storage medium;

first program instructions to computer usable program code for, in response to changing said present name of said first versioned object to a different name, said different name having been used by a second versioned object, said first versioned object being a first file, said present name being a file name of said first file, said second versioned object being a second file, said second file being different from said first file, said different name being a file name of said second file, said different name not being used by a previous version of said first versioned object, said second versioned object using said different name being associated with an existing version number comprising delimiter-separated components having a starting component and an ending component, said starting component being a left-most component of said delimiter-separated components, said ending component being a right-most component of said delimiter-separated components,

identify a value of said starting component of said existing version number associated with said second versioned object; and

generate a new version number for said first versioned object having said different name, said new version number comprising a new plurality of components, wherein a value of a new starting component of said new plurality of components of said new version number is different from said value of said starting component of said existing version number associated with said second versioned object, said new starting component being a left-most component of said new plurality of components of said new version number;

wherein in response to said different name being associated with a first successor of said first versioned object with respect to said present version number, said first program instructions to generate said new version number increments a value of an ending component of said present version number to provide a new ending component of said new plurality of components of said new version number, said new ending component being at a right- most component of said new plurality of components;

wherein in response to said different name being associated with an nth successor of said first versioned object with respect to said present version number, where n is greater than one, said first program instructions to generate said new version number appends a component pair comprising a pair component equal to n−

1 and another pair component equal to a predetermined value to a right end of said new version number; and

wherein said first program instructions are stored on said computer readable storage medium.

7. The article of manufacture of claim 6 wherein a third versioned object having another existing version number uses said different name, said another existing version number comprising another delimiter-separated components having another starting component and another ending component, said third versioned object being a third file, wherein said first program instructions to identify identifies a highest value of said starting component of said existing version number associated with said second versioned object and said another starting component of said another existing version number associated with said third versioned object, and said first program instructions to generate said new version number increments said highest value by a predetermined value to provide an incremented value, and said new starting component of said new plurality of components of said new version number is set to said incremented value.

8. The article of manufacture of claim 6 wherein said new plurality of components of said new version number is a delimiter-separated series of components.

9. The article of manufacture of claim 6 wherein a uniform resource identifier (URI) comprises said different name and said new version number.

10. The article of manufacture of claim 9 further comprising:

second program instructions to display said first versioned object associated with said URI, wherein said second program instructions are stored on said computer readable storage medium.

11. A computer system providing a version number of a first versioned object having a present name and a present version number, comprising:

a processor; and

a memory, storing instructions that when executed cause said processor to;

in response to changing said present name of said first versioned object to a different name, said different name having been used by a second versioned object, said first versioned object being a first file, said present name being a file name of said first file, said second versioned object being a second file, said second file being different from said first file, said different name being a file name of said second file, said different name not being used by a previous version of said first versioned object, said second versioned object using said different name being associated with an existing version number comprising delimiter-separated components having a starting component and an ending component, said starting component being a left-most component of said delimiter-separated components, said ending component being a right-most component of said delimiter-separated components,

identify a value of said starting component of said existing version number associated with said second versioned object; and

generate a new version number for said first versioned object having said different name, said new version number comprising a new plurality of components, wherein a value of a new starting component of said new plurality of components of said new version number is different from said value of said starting component of said existing version number associated with said second versioned object, said new starting component being a left-most component of said new plurality of components of said new version number;

wherein in response to said different name being associated with a first successor of said first versioned object with respect said present version number, said instructions to generate said new version number increments a value of an ending component of said present version number to provide a new ending component of said new plurality of components of said new version number, said new ending component being a right-most component of said new plurality of components of said new version number; and

wherein in response to said different name being associated with an nth successor of said first versioned object with respect to said present version number, where n is greater than one, said instructions to generate said new version number appends a component pair comprising a pair component equal to n−

1 and another pair component equal to a predetermined value to a right end of said new version number.

12. The computer system of claim 11 wherein said value of said new starting component of said new version number is greater than said value of said starting component of said existing version number associated with said second versioned object using said different name.

13. The computer system of claim 11 wherein said components are integers.

14. The computer system of claim 11 wherein a uniform resource identifier (URI) comprises said different name and said new version number.

15. A computer-implemented method of providing a version number of a first versioned object having a present name and a present version number, comprising:

in response to changing said present name of said first versioned object to a different name, thereby producing a new version of said first versioned object, said first versioned object being a first file, said present name being a file name of said first file, said different name having been used by a second versioned object, said second versioned object being a second file, said second file being different from said first file, said different name being a file name of said second file, said different name not being used by a previous version of said first versioned object, said second versioned object using said different name being associated with an existing version number comprising delimiter-separated integers having a starting integer and an ending integer, said starting integer being a left-most integer of said delimiter-separated integers, said ending integer being a right-most integer of said delimiter-separated integers, wherein said first file is not a version of said second file, and said second file is not a version of said first file,

identifying a value of said starting integer of said existing version number associated with said second versioned object;

in response to said new version of said first versioned object being a first successor with respect to said present version number, generating a first new version number comprising a new plurality of delimiter-separated integers for said first versioned object using said different name, wherein a value of a starting integer of said new plurality of delimiter-separated integers of said first new version number is different from said value of said starting integer of said existing version number associated with said second versioned object, said starting integer of said new plurality of delimiter-separated integers of said new version number being a left-most integer, and a value of an ending integer of said new plurality of delimiter-separated integers of said first new version number is set to a value of an ending integer of said present version number plus one; and

in response to said new version of said first versioned object being a second successor with respect to said present version number, generating a second new version number comprising another new plurality of delimiter-separated integers for said first versioned object using said different name, wherein a value of a starting integer of said another new plurality of delimiter-separated integers of said second new version number is different from said value of said starting integer of said existing version number associated with said second versioned object, said starting integer of said another new plurality of delimiter-separated integers of said second new version number being a left most integer, and a component pair of (1.0) is appended to a right end of said second new version number.