Data processing system with data recovery

• US 20030195899A1
• Filed: 11/08/2002
• Published: 10/16/2003
• Est. Priority Date: 11/09/2001
• Status: Active Grant

• Current Assignee: Yozosoft Company Limited
• Original Assignee: WUXI Evermore Software Incorporated
• Inventors: Tsao, Sheng A.
• Granted Patent: US 7,325,160 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A data processing system including an application program including means for generating and editing data files, each data file including an array of main data objects that each have a unique address with respect to the other main data objects of the array, means for storing the data files in non-volatile memory, wherein the means for generating includes means for receiving in working memory user input defining the address of a main data object of a particular data file, and elements to be included therein, means for determining completion of the main data object, and means for appending the completed data object with the address thereof to a stored counterpart of the data file. The application program also includes means for identifying a most recently appended data object having a particular address, and means for inserting the most recently appended data object as one of the main data objects, whereby, in the event that the content of the working memory is lost, the content of the data file, including the most recently appended data object, is recoverable from the stored counterpart of the data file./

Claims

1. A data processing system comprising an application program for user interaction with stored data, comprising:

(a) means for generating and editing data files, each data file comprising an array of main data objects, each of the main data objects having a unique address with respect to the other main data objects of the array;

(b) means for storing the data files in non-volatile memory;

(c) the means for generating comprising;

(i) means for receiving in working memory user input defining the address of a main data object of a particular data file, and elements to be included therein;

(ii) means for determining completion of the main data object; and

(iii) means for appending the completed data object with the address thereof to a stored counterpart of the data file;

(d) means for identifying a most recently appended data object having a particular address; and

(e) means for inserting the most recently appended data object as one of the main data objects,

whereby, in the event that the content of the working memory is lost, the content of the data file, including the most recently appended data object, is recoverable from the stored counterpart of the data file.

2. The system of claim 1, wherein generating and editing is performed in sessions, the system further comprising means for appending a version mark to the stored counterpart of the data file at the conclusion of each session, the version mark being distinguishable from other version marks appended to the stored counterpart of the data file.

3. The system of claim 2, wherein the version mark comprises date and time information.

4. The system of claim 3, wherein the version mark further comprises author information.

5. The system of claim 3, wherein the version mark further comprises application information.

6. The system of claim 2, further comprising means for activation of the data file to an intermediate state corresponding to a user selected version.

7. The system of claim 2, further comprising means for activation of the data file to plural intermediate states corresponding to a sequence of versions.

8. The system of claim 7, further comprising means for selecting a particular one of the plural intermediate states for further user interaction.

9. The system of claim 8, further comprising:

(a) means for selectively accepting and rejecting particular data objects associated with the selected intermediate state corresponding to a selected version;

(b) means for selectively accepting a terminal subset of the data objects associated with the selected version; and

(c) means for selectively accepting and rejecting a terminal subset of the data objects associated with the selected version together with all subsequent versions.

10. The system of claim 1, wherein the editing is performed in sessions, the editing including operations affecting multiple data objects, and wherein the means for generating further comprises:

(a) means for recording a macro of operations to be performed on data objects as defined in an editing session;

(b) means for appending the macro to the stored counterpart of the data file; and

(c) means for executing the macro in a subsequent editing session.

11. The system of claim 10, wherein the means for executing the macro is activated upon activation of the data file.

12. The system of claim 1, wherein the means for executing the macro is activated upon deactivation of the data file.

13. A method for data processing using an application program, comprising:

(a) generating a data file comprising an array of data objects, wherein each object includes an object address;

(b) storing the data file in non-volatile memory;

(c) receiving in working memory user input defining the address of a main data object, and elements to be included therein;

(d) determining completion of the main data object;

(e) appending the completed data object with the address thereof to a stored counterpart of the data file;

(f) identifying a most recently appended data object having a particular address; and

(g) inserting the most recently appended data object as one of the main data objects.

14. The method of claim 13, further comprising:

(a) editing the data file, the generating and editing being performed in sessions during which the data file is active; and

(b) appending a version mark to the stored counterpart of the data file at the conclusion of each session, the version mark being distinguishable from other version marks appended to the stored counterpart of the data file.

15. The method of claim 14, wherein the appending comprises including date and time information in association with the version mark.

16. The method of claim 15, wherein the appending further comprises including author information in association with the version mark.

17. The system of claim 15, wherein the appending further comprises including application information in association with the version mark.