-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Furthermore, the routing algorithm is the same for inserts as for > requests, so overlaps occur for inserts as well. If someone inserts under > key "mp3" it goes onto 5-10 nodes. Assuming we allow multiple docs per > key, every such insert will overlap with each other on at least one of > those 5-10 nodes. (And once the two paths cross they will probably join > and stay together for the remainder of the HTL.) Therefore there will > be nodes which will have at least 1/5 to 1/10 of all "mp3" keys stored > in Freenet. Yep.. Thats my concern as well. And it follows from the way freenet operates. You may have 5-10 hops, but those hops are designed to traverse as much of freenet as possible since each server makes its 'best guess' as to which server has the data. We don't want data clustered. This is why storing by CHK is appealing to me. The hash of any two documents is likely to be wildly different, even if they themselves differ by only a single bit. Thus like files will be scattered over the network so there is no one point of failure.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE4/yNvpXyM95IyRhURAh5cAJ9bSl9ndzEdcVJmw+sDtLmlg0QsxwCfdGHm 2WavDLu644fe0H2EIE2y6Q4= =T1LH -----END PGP SIGNATURE----- _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
