2013-07-02 05:26:44 +00:00
|
|
|
5f053cc6143f2624ade4ff193b2ae0dfa2fc8b68
|
|
|
|
|
|
|
|
|
|
This file's random string on the first line is an optimization and
|
|
|
|
|
paranoia facility for clients.
|
|
|
|
|
|
|
|
|
|
If the client sees the same random string in multiple upload sessions,
|
|
|
|
|
it assumes that the blobserver still has all the same blobs, and also
|
|
|
|
|
it's the same server. This mechanism is not fundamental to
|
2018-01-30 11:02:56 +00:00
|
|
|
Perkeep's operation: the client could also check each blob before
|
2013-07-02 05:26:44 +00:00
|
|
|
uploading, or enumerate all blobs from the server too. This is purely
|
|
|
|
|
an optimization so clients can mix this value into their "is this file
|
|
|
|
|
uploaded?" local cache keys.
|
|
|
|
|
|
|
|
|
|
If you deleted any blobs (or suspect any were corrupted), it's best to
|
|
|
|
|
delete this file so clients can safely re-upload them.
|
|
|
|
|
|
