On Mon, Feb 17, 2003 at 04:54:34PM -0500, Andrew Rodland wrote: > On Monday 17 February 2003 03:49 pm, Matthew Toseland wrote: > > On Mon, Feb 17, 2003 at 11:36:34AM +0100, [EMAIL PROTECTED] wrote: > > > hello list... > > > > > > i wonder why the insertion of a file with key CHK@ (automatically > > > generate the chk value) results different CHK-keys when inserted with fcp > > > and with fproxy > > > > > > these two different metadata headers of course produce different CHK@s > > > due do different metadata, but the data itself is the same > > > > You have answered your own question. The client we provide, java > > freenet.client.cli.Main (which uses FCP), will (hopefully) produce > > identical keys to what fproxy produces. > > > perhaps a checkbox in the web-frontend "create fcp compatible keys" or > > > "don't add additional metadata" would suffice for user interaction. > > > > Um, no. FCP clients (*COUGH* FROST *COUGH*) should provide the > > appropriate metadata. I have no idea what the point is of > > Info.Description=file is though. > > There are lots of legitimate reasons for CHK's to be inserted without > metadata; in fact it's usually the better case. I wouldn't mind seeing fproxy > be able to do this without hassle.
There are precisely two reasons. One is that it is a chunk in a splitfile, the other is that it is a file that has been redirected to by an SSK (possibly a manifest). These are two very similar cases. And there are tools which will let you do this. The trivial solution to get fproxy to do it would be to always create a redirect even if the file is a CHK, just to not include the metadata. However I am absolutely not going to do this, except maybe as an option. Because many sites DO insert files as CHKs and then link to them as /CHK@<blah>/<preferred filename> And I see no pressing reason to implement such an option. -- Matthew Toseland [EMAIL PROTECTED][EMAIL PROTECTED] Full time freenet hacker. http://freenetproject.org/ Freenet Distribution Node (temporary) at http://amphibian.dyndns.org:8889/LBRuUIF0afM/ ICTHUS.
msg06876/pgp00000.pgp
Description: PGP signature
