File caching method and apparatus
First Claim
Patent Images
1. A method of managing data files in a file caching server that provides access to a plurality of stored data files, said method comprising:
- receiving a request for a file identified by a cryptographically secure checksum;
determining if said file resides on said file caching server using said cryptographically secure checksum and, if said file resides on said file caching server, retrieving said file from said file caching server;
if said file does not reside on said file caching server, then requesting from another file server, a remote file identified by said cryptographically secure checksum.
2 Assignments
0 Petitions
Accused Products
Abstract
A method of managing data files in a file caching server provides access to a plurality of stored data files. The method is to receive a request for a file, which is identified by a cryptographically secure checksum. The availability of the file is determined using the cryptographically secure checksum and, if said file is available, retrieving the file. If the file is not available to said file caching server, then a file request is issued to, and the file is retrieved from another file server where the file with the cryptographically secure checksum exists.
-
Citations
25 Claims
-
1. A method of managing data files in a file caching server that provides access to a plurality of stored data files, said method comprising:
-
receiving a request for a file identified by a cryptographically secure checksum;
determining if said file resides on said file caching server using said cryptographically secure checksum and, if said file resides on said file caching server, retrieving said file from said file caching server;
if said file does not reside on said file caching server, then requesting from another file server, a remote file identified by said cryptographically secure checksum. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A method of managing flies on a file caching server, comprising:
-
receiving, at said file caching server, a file save request including a file to be saved on said file caching server and a file name associated with said file under which said file is to be saved;
determining a cryptographically secure checksum from contents of said file;
prior to saving said file, determining if said file is stored on said file caching server by the presence of the cryptographically secure checksum in said file caching server;
if the cryptographically secure checksum is not present in said file caching server, then storing the file, the file name, and the cryptographically secure checksum within the file caching server. - View Dependent Claims (7)
-
-
8. A data network comprised of:
a file caching server capable of receiving requests for files from client computers operatively coupled to said file caching server, the file caching server identifying requested files by a cryptographically secure checksum, said file caching server delivering to a client a locally stored copy of the requested file if said requested file is identified by said cryptographically secure checksum as being stored on said file caching server, and said file caching server delivering to the client a remotely stored copy of the requested file obtained from a file server if said requested file is not identified by said cryptographically secure checksum.
-
9. A data network comprised of:
a file server capable of storing files from a file caching server operatively coupled to said file server, the file server identifying a file to be stored by a cryptographically secure checksum, said file server storing said file from said file caching server if said file is not identified as being stored on said file server by the presence in said file server of said cryptographically secure checksum.
-
10. Data storage media configured to store executable computer program instructions to cause a computer to:
-
receive a request for a file which is identified by a cryptographically secure checksum;
determining if said file resides on said computer using said cryptographically secure checksum and, if said file resides on said computer, retrieving said file from said computer;
if said file does not reside on said computer, then requesting from a second computer a remote file identified by said cryptographically secure checksum.
-
-
11. A method of managing the transfer of a plurality of associated data files between a server and a client having a plurality of files to send to said server, said method comprising:
-
said client calculating a cryptographically secure checksum for at least a first file of said plurality of files;
said client determining if said server has a file with an identical cryptographically secure checksum;
if said server has a file with an identical cryptographically secure checksum, determining that said server has a copy of said first file;
if said server does not have a file with an identical cryptographically secure checksum, sending said first file to said server by said client. - View Dependent Claims (12, 13, 14, 15, 16)
-
-
17. A method of managing the transfer of a plurality of associated data files between a server and a client having a plurality of files to send to a server, said method comprising:
-
said client calculating a checksum for each file of said plurality of files;
said client sending each of said plurality of files to said server;
modifying at least one of said plurality of files;
said client recalculating the checksum for each of said plurality of files;
said client determining which of the flies stored on said server have checksums that do not match the recalculated checksums;
said client re-sending to said server, only the files stored on the server whose checksums do not match the recalculated checksums on the client. - View Dependent Claims (18, 19, 20, 21, 22)
-
-
23. A method of managing the transfer of a plurality of associated data files between a server and a client having a plurality of files to send to said server, said method comprising:
-
said server receiving said plurality of files;
said server calculating a checksum for each file and storing the server-calculated checksums in a first list;
said server receiving a second list of client-calculated checksums from said client;
said server identifying to said client, checksums in the second list that are not in the first list;
said server receiving from said client, files whose checksums were not in the second list. - View Dependent Claims (24, 25)
-
Specification