> Someone told me that there would be no metadata permitted in 0.4 CHKs.
> If this is true then it needs to be rethought - I can imagine no reason
> why client-side metadata would not be permitted. For example, it would
> prevent web browsers from displaying documents referenced by CHKs.
As has been discussed on the mailing list, the only way to have two copies
of the same file collide when inserted and also not allow the first
inserter to have total control over the contents of the metadata is to not
put metadata in CHKs.
Metadata for CHKs can be stored in a separate document. For split files,
nothing has changed, since you have to request the manifest before you can
request the data and you can put the metadata in the manifest. For
non-split files, you can use a redirect. If the cost of doing two requests
in order to obtain the file is unpleasant, Adam has suggested the clever
idea of adding the key for the file containing the metadata as an optional
part of the CHK so that it can be passed around with the key for the file.
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl
