US2008010378A1PendingUtilityA1

Collaborative File Update System

52
Assignee: PARKER JAMES APriority: Jul 10, 2003Filed: Aug 3, 2007Published: Jan 10, 2008
Est. expiryJul 10, 2023(expired)· nominal 20-yr term from priority
G06Q 10/10Y10S707/99954Y10S707/99953
52
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

In a disclosed method facilitates collaborative file updating, data is accepted from one of a plurality of users and stored. The data represents an initial version of the file and designates one or more recipients of the initial version. Then, for each one of sequentially updated versions of the file, data representing a difference between the updated version of the file and an immediately previous version of the file is accepted from a user. The data also designates one or more recipients of the updated version. Data representative of the updated version of the file is transmitted to the designated recipients of the updated version. The data transmitted to each recipient who is designated as a recipient of the updated version and who accessed the immediately previous version consists substantially of the difference between the updated and previous versions of the file. Other methods and systems are disclosed.

Claims

exact text as granted — not AI-modified
1 - 29 . (canceled)  
     
     
         30 . A method for managing transmission of versions of a file among a plurality of users, the method comprising: 
 (a) storing a first data set received from a first user that is representative of a first version of the file;    (b) transmitting the first data set to the second user as a result of the second user having activated a reference to the first version, which reference is contained in an e-mail message received from the first user;    (c) storing a second data set received from the second user that is representative of the difference between a second version of the file and the first version of the file; (d) transmitting the second data set to the first user as a result of the first user having activated a reference to the second version, which reference is contained in an e-mail message received from the second user; and    (e) as a result of the third user having activated a reference to the second version, which reference is contained in an e-mail message received from the second user, (1) patching the first version of the file with the second data set, thereby creating a third data set representing the second version of the file; and (2) transmitting the third data set to the third user.    
     
     
         31 . The method of  claim 30  further comprising storing data in a separate file data set for each one of the plurality of users.  
     
     
         32 . The method of  claim 31  further comprising generating separate plausibly unique identification codes associated with respective ones of the plurality of users, wherein each data file includes in its name at least a portion of a respective identification code.  
     
     
         33 . A data storage medium comprising indicia of instructions for one or more processors to perform a method for managing transmission of versions of a file among a plurality of users, the method comprising: 
 (a) storing a first data set received from a first user that is representative of a first version of the file;    (b) transmitting the first data set to the second user as a result of the second user having activated a reference to the first version, which reference is contained in an e-mail message received from the first user;    (c) storing a second data set received from the second user that is representative of the difference between a second version of the file and the first version of the file; (d) transmitting the second data set to the first user as a result of the first user having activated a reference to the second version, which reference is contained in an e-mail message received from the second user; and    (e) as a result of the third user having activated a reference to the second version, which reference is contained in an e-mail message received from the second user, (1) patching the first version of the file with the second data set, thereby creating a third data set representing the second version of the file; and (2) transmitting the third data set to the third user.    
     
     
         34 . The data storage medium of  claim 33  wherein the method further comprises storing data in a separate file data set for each one of the plurality of users.  
     
     
         35 . The data storage medium of  claim 34  wherein the method further comprises generating separate plausibly unique identification codes associated with respective ones of the plurality of users, wherein each data file includes in its name at least a portion of a respective identification code.  
     
     
         36 . A file server accessible to a plurality of users including a first, second, and third user, the file server comprising: 
 (a) means for storing a first data set received from a first user that is representative of a first version of the file;    (b) means responsive to the second user having activated a reference to the first version, which reference is contained in an e-mail message received from the first user, for transmitting the first data set to the second user;    (c) means for storing a second data set received from the second user that is representative of the difference between a second version of the file and the first version of the file;    (d) means responsive to the first user having activated a reference to the second version, which reference is contained in an e-mail message received from the second user, for transmitting the second data set to the first user; and    (e) means responsive to the third user having activated a reference to the second version, which reference is contained in an e-mail message received from the second user, for (1) patching the first version of the file with the second data set, thereby creating a third data set representing the second version of the file; and (2) transmitting the third data set to the third user.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.