Application-managed file versioning
First Claim
1. One or more computer memory storage components having stored thereon multiple instructions that, when executed by one or more processors of a device, cause the one or more processors to implement a versioning module of an operating system executable on the device, the versioning module configured to:
- receive, from an application that opens and edits a file, a request associated with an application-managed file versioning of the file to store a new version of the file, the request automatically generated by the application responsive to the application detecting an application-specific event, the versioning module configured to receive requests to store new versions of files from multiple different applications that each employ different criteria to determine when to create the new versions of files;
generate a filename for the new version of the file responsive to the request, the filename including a first portion having at least a portion of a name of the file, and a second portion having data indicating that the new version of the file is a version of the file, the filename further including one or more flags designated by the application to be set in the filename by the versioning module, at least one flag indicating that auto-versioning and application-managed file versioning are to be performed by the versioning module with respect to the new version of the file, the filename further including a timestamp portion that identifies a date and time at which the new version of the file is created;
store the new version of the file; and
based on the at least one said flag being set in the filename, perform the auto-versioning by at least automatically generating an additional new version of the file at particular intervals of time.
2 Assignments
0 Petitions
Accused Products
Abstract
In accordance with one or more aspects of the application-managed file versioning, a request to store a new version of a file is received from an application, the request having been generated by the application. A filename for the new version of the file is generated, derived from a standardized naming convention. The filename includes a first portion having at least a portion of a name of the file, and a second portion having data indicating that the new version of the file is a version of the file. A set of application programming interfaces (APIs) can be exposed that allow the application to manage file versions, such as creating a new version of a file, identifying one or more versions of the file, listing one or more versions of the file, and deleting one or more versions of the file.
36 Citations
20 Claims
-
1. One or more computer memory storage components having stored thereon multiple instructions that, when executed by one or more processors of a device, cause the one or more processors to implement a versioning module of an operating system executable on the device, the versioning module configured to:
-
receive, from an application that opens and edits a file, a request associated with an application-managed file versioning of the file to store a new version of the file, the request automatically generated by the application responsive to the application detecting an application-specific event, the versioning module configured to receive requests to store new versions of files from multiple different applications that each employ different criteria to determine when to create the new versions of files; generate a filename for the new version of the file responsive to the request, the filename including a first portion having at least a portion of a name of the file, and a second portion having data indicating that the new version of the file is a version of the file, the filename further including one or more flags designated by the application to be set in the filename by the versioning module, at least one flag indicating that auto-versioning and application-managed file versioning are to be performed by the versioning module with respect to the new version of the file, the filename further including a timestamp portion that identifies a date and time at which the new version of the file is created; store the new version of the file; and based on the at least one said flag being set in the filename, perform the auto-versioning by at least automatically generating an additional new version of the file at particular intervals of time. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method implemented in a computing device, the method comprising:
-
receiving at a versioning module, from an application that opens and edits a file, a request associated with an application-managed file versioning of the file to store a new version of the file, the request automatically generated by the application responsive to the application detecting an application-specific event, the versioning module configured to receive requests to store new versions of files from multiple different applications that each employ different criteria to determine when to create the new versions of files; generating, by the versioning module, a filename for the new version of the file responsive to the request, the filename including a first portion having at least a portion of a name of the file, and a second portion having data indicating that the new version of the file is a version of the file, the filename further including one or more flags designated by the application to be set in the filename by the versioning module, at least one flag indicating that auto-versioning and application-managed file versioning are to be performed by the versioning module with respect to the new version of the file, the filename further including a timestamp portion that identifies a date and time at which the new version of the file is created; storing the new version of the file; and based on the at least one said flag being set in the filename, performing the auto-versioning by at least automatically generating an additional new version of the file at particular intervals of time. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
-
-
17. A system comprising:
-
one or more processors; and one or more computer-readable memory storage components having stored thereon computer-executable instructions which are executable by the one or more processors to implement a versioning module configured to; receive, from an application that opens and edits a file, a request associated with an application-managed file versioning of the file to store a new version of the file, the request automatically generated by the application responsive to the application detecting an application-specific event, the versioning module configured to receive requests to store new versions of files from multiple different applications that each employ different criteria to determine when to create the new versions of files; generate a filename for the new version of the file responsive to the request, the filename including a first portion having at least a portion of a name of the file, and a second portion having data indicating that the new version of the file is a version of the file, the filename further including one or more flags designated by the application to be set in the filename by the versioning module, at least one flag indicating that auto-versioning and application-managed file versioning are to be performed by the versioning module with respect to the new version of the file, the filename further including a timestamp portion that identifies a date and time at which the new version of the file is created; store the new version of the file; and based on the at least one said flag being set in the filename, perform the auto-versioning by at least automatically generating an additional new version of the file at particular intervals of time. - View Dependent Claims (18, 19, 20)
-
Specification