Versioning in internet file system

• US 8,335,775 B1
• Filed: 05/15/2000
• Issued: 12/18/2012
• Est. Priority Date: 08/05/1999
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Sedlar, Eric, Roberts, Michael J.
• Primary Examiner(s): LIN, SHEW FEN
• Application Number:
  US09/571,696
• Time in Patent Office: 4,600 Days
• Field of Search: 707 1- 4, 707 8- 10, 707100-1041, 707200-205, 707/500, 707/511, 707/695, 707/638, 707/809, 711/100, 711120-122, 717/100, 717120-123, 717168-170, 715/500, 715/511, 715/229
• US Class Current: 707/695
• CPC Class Codes: G06F 16/176 Support for shared access to files; File sharing support
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

Techniques are provided for managing file versions. In one technique, versions of directories are created responsive to creation of versions of files descendant from the directories. Directory versions are associated with times. Interfile links are maintained so file versions descendant from a directory version reflect the directory version'"'"'s time. In another technique, a mechanism is provided for tagging file versions that shouldn'"'"'t be overwritten. Responsive to a first file version'"'"'s update, it is determined whether that version is tagged. If so, a second version is stored while retaining the first version. Otherwise, the first version is deleted responsive to the second version'"'"'s storage. In another technique, responsive to a first file version'"'"'s change, it is determined whether first criteria are satisfied. If so, a second version is created while retaining the first version, and versions of the file'"'"'s ancestor files that satisfy second criteria are created.

Claims

1. A computer-implemented method for managing versions of files in a file system, the method comprising the steps of:

providing a mechanism for tagging versions of files that are not to be overwritten;

as part of an update to a first version of a file, performing the steps of;

traversing one or more files in a file hierarchy to locate said first version of the file;

determining whether any file in a plurality of files is tagged, wherein the plurality of files consists of the first version of the file and the one or more files traversed to locate said first version of the file;

if one of the one or more traversed files is tagged or if the first version of the file is tagged, then storing a second version of the file while retaining said first version of the file; and

if none of the one or more traversed files and the first version of the file is tagged, then storing said second version of the file and deleting said first version of the file;

wherein the steps are performed on one or more computing devices.

2. The method of claim 1 wherein:

the first version of said file is stored in a first version of a particular directory;

the first version of the particular directory includes one or more files other than said file;

the step of storing said second version of the file while retaining said first version of the file includes;

creating a second version of said particular directory;

establishing said one or more files as members of said second version of said particular directory; and

establishing said second version of said file as a member of said second version of said particular directory while maintaining said first version of said particular file as a member of said first version of said particular directory.

3. A computer-implemented method for maintaining versions of files in a file system, the method comprising the steps of:

as part of a change made to a first version of a file, determining whether a first set of criteria is satisfied;

if the first set of criteria is satisfied, then

creating and storing a second version of the file while retaining the first version of the file; and

for each ancestor file, of one or more ancestor files above said file in a file hierarchy,

determining whether said each ancestor file satisfies a second set of criteria;

if said each ancestor file satisfies said second set of criteria, then creating and storing a new version of said each ancestor file;

if said each ancestor file does not satisfy said second set of criteria, then not creating and storing a new version of said each ancestor file;

wherein the steps are performed on one or more computing devices.

4. The method of claim 3 further comprising the steps of:

receiving user input that specifies that one or more files in said file system are to be tagged;

storing data within said file system to indicate that said one or more files are tagged;

wherein the step of determining whether a first set of criteria is satisfied includes determining whether said first version of said file is tagged; and

wherein said first set of criteria includes that said first version of said file is tagged.

5. The method of claim 3 further comprising the step of associating said file with a project, wherein said second set of criteria includes that said ancestor file belongs to said project.

6. The method of claim 5 wherein the file system includes one or more files that belong to a second project, the method further including the step of allowing a user to use a view of said file system in which files that belong to said project are seen as they existed at a first point in time, and the one or more files that belong to the second project are seen as they existed at a second point in time that is different from said first point in time.

7. The method of claim 6 further comprising the steps of:

through said view, performing a traversal of said file hierarchy based on links between files in said file system; and

during said traversal, following a link that has a source file and a target file only if said view specifies that said source file and said target file are to be seen as of a same point in time.

8. The method of claim 4 further comprising the step of deleting a third version of said file that is not tagged in response to creating said second version of the file.

9. The method of claim 8 wherein the step of deleting said third version of said file is performed in response to detecting that creation of said second version of the file would exceed a threshold maximum number of untagged versions of said file.

10. The method of claim 7, further comprising the step of marking links in said file system to indicate whether the source file and the target file associated with the links belong to the same project.

11. One or more storage media storing instructions for managing versions of files in a file system, wherein the instructions, when executed by one or more processors, cause:

providing a mechanism for tagging versions of files that are not to be overwritten;

as part of an update to a first version of a file, performing the steps of;

traversing one or more files in a file hierarchy to locate said first version of the file;

determining whether any file in a plurality of files is tagged, wherein the plurality of files consists of the first version of the file and the one or more files traversed to locate said first version of the file;

if one of the one or more traversed files is tagged or if the first version of the file is tagged, then storing a second version of the file while retaining said first version of the file; and

if none of the one or more traversed files and the first version of the file is tagged, then storing said second version of the file and deleting said first version of the file.

12. The one or more storage media of claim 11, wherein:

the first version of said file is stored in a first version of a particular directory;

the first version of the particular directory includes one or more files other than said file;

the step of storing said second version of the file while retaining said first version of the file includes;

creating a second version of said particular directory;

establishing said one or more files as members of said second version of said particular directory; and

establishing said second version of said file as a member of said second version of said particular directory while maintaining said first version of said particular file as a member of said first version of said particular directory.

13. One or more storage media storing instructions for maintaining versions of files in a file system, wherein the instructions, when executed by one or more processors, cause:

as part of a change made to a first version of a file, determining whether a first set of criteria is satisfied;

if the first set of criteria is satisfied, then

creating and storing a second version of the file while retaining the first version of the file; and

for each ancestor file, of one or more ancestor files above said file in a file hierarchy,

determining whether said each ancestor file satisfies a second set of criteria;

if said each ancestor file satisfies said second set of criteria, then creating and storing a new version of said each ancestor file;

if said each ancestor file does not satisfy said second set of criteria, then not creating and storing a new version of said each ancestor file.

14. The one or more storage media of claim 13, wherein the instructions, when executed by the one or more processors, further cause:

receiving user input that specifies that one or more files in said file system are to be tagged;

storing data within said file system to indicate that said one or more files are tagged;

wherein the step of determining whether a first set of criteria is satisfied includes determining whether said first version of said file is tagged; and

wherein said first set of criteria includes that said first version of said file is tagged.

15. The one or more storage media of claim 14, wherein the instructions, when executed by the one or more processors, further cause deleting a third version of said file that is not tagged in response to creating said second version of the file.

16. The one or more storage media of claim 15, wherein deleting said third version of said file is performed in response to detecting that creation of said second version of the file would exceed a threshold maximum number of untagged versions of said file.

17. The one or more storage media of claim 13, wherein the instructions, when executed by the one or more processors, further cause associating said file with a project, wherein said second set of criteria includes that said ancestor file belongs to said project.

18. The one or more storage media of claim 17, wherein the file system includes one or more files that belong to a second project, wherein the instructions, when executed by the one or more processors, further cause allowing a user to use a view of said file system in which files that belong to said project are seen as they existed at a first point in time, and the one or more files that belong to the second project are seen as they existed at a second point in time that is different from said first point in time.

19. The one or more storage media of claim 18, wherein the instructions, when executed by the one or more processors, further cause:

through said view, performing a traversal of said file hierarchy based on links between files in said file system; and

during said traversal, following a link that has a source file and a target file only if said view specifies that said source file and said target file are to be seen as of a same point in time.

20. The one or more storage media of claim 19, wherein the instructions, when executed by the one or more processors, further cause marking links in said file system to indicate whether the source file and the target file associated with the links belong to the same project.