On Thu, 23 Apr 2009 14:16:40 +0100, Matthew Toseland wrote: > GORY DETAILS: > > Currently we use: > CHK@<routing key>,<crypto key>,<extra> > > (Filenames afterwards are manifests, and therefore impact on the CHK)
Isn't the first part supposed to be the data hash, and not a routing key. And what is a routing key anyways? :P How does the filename impact the hash again? > The new key type would be: > > DHK@<data hash>,<routing key 1>,<routing key 2>,<routing key > 3>,<extra>/<ignore filename> > > (A filename is mandatory, and is always ignored, so does not impact > on the rest of the key). So the DHK filename part is mandatory, but is simply a recommendation? So, if the filenames here don't impact on the hash, this should help in the case where the same file gets uploaded with different filenames? (Ie., from your description of CHK filenames above, differently named files each have different manifests, and thus waste both disk space and key space?)
