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
i know that fproxy adds a bigger metadata header to the inserted file: >> Version Revision=1 EndPart Document Info.Format=application/x-macbinary Info.Description=file End << fcp only adds: >> Version Revision=1 EndPart << these two different metadata headers of course produce different CHK@s due do different metadata, but the data itself is the same i suspect that inserting the same file via fcp and fproxy should create a key collision, no matter what! is there a way to upload "raw, untainted" data (only including the short header that fcp uses) with fproxy, so the inserts can collide clean? perhaps a checkbox in the web-frontend "create fcp compatible keys" or "don't add additional metadata" would suffice for user interaction. when left at the current situation, one cannot reinsert a fallen off file which is mentioned in the site's map via fproxy, because it generates a different chk-key as when the site was inserted via fcp! think about it. surely it's just a small impact to the code, but it produces more unanimous behavior have a nice week :) _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
