"Scott G. Miller" writes: > > The other problem is that the windows filesystem gets somewhat ungainly > slow with large numbers of files in a directory. This should > be solved by having a tree structure. Implementing the DS in the=20 > filesystem again is almost easy, except for the routing table.
It's ungainly in nearly every system, except for some experimental ones. However, I did reference two systems that do exactly what I'm proposing and apparently spent more time thinking about this then people belive. Space usage: Constant and stable. No surprises here. (Come ON people, we're powers-of-two bounded! There's no such thing as a 4.2k block filesystem) Directory size: store/ab/cd/(ef?)/abcdefg. As for VFAT performance, I'm not that worried. Every dammed program in windows dumps millions of tiny files around and lets the OS handle it. (every game released in the past 5 years, Internet Explorer, etc) Here's the security problems posed (if running paranoid): You have a number of doubly encrypted files with encrypted filenames, but actual sizes and (filesystem dependant) timestamps. Is this enough to worry about? Blowing away the node key means you won't be able to decrypt any files, or even reverse the filenames. Unlike the current DS, we won't have varying keys since I can't think of a portable way to seed the crypto. --Dan _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
