> Um, before the Freenet interface is totally solidified, I think file > size and splitting should be addressed. I'd be in favor of Freenet > being incapable of accepting anything bigger or smaller than 65536 bytes > (2^16). I chose this number so there can be a 2 byte "data length" > field. I'd *like* to say limit to 65536 bytes, but I just can't, because it tickles my no-no button for security. Having a large file (say multi-megabytes) split into that many chunks means that you might have to access a very large chunk of freenet to retrieve it. I don't like the bandwidth ramifications because its starts to approach the nasty B-word.
I think that a file being split into more than 10-15 parts is excessive. > At the same time, there needs to be some sort of metadocument thing to > list all the parts that make up a particular file. This is more of a > client issue, but these two kind of go hand in hand in my opinion. Easily solved already. We have document-private metadata. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20000730/899dbc21/attachment.pgp>
