-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Key collisions aren't a problem if you keep them in different > tables. Getting the right document isn't a problem if the different > message types look in the different tables. Clustering works the same as > before. True, if a KHK and a CHK are the same value they will go to the > same node, but that isn't important since they will be unrelated so > whether they end up on the same node or not isn't important. Actually, > they'd only be the same if the key for the first was equal to the data of > the second, which would be silly. I'm inclined to think that the simplest solution is the best. That is to say the one that divides the _appearance_ of the different content addressing types as little as possible. We should also keep in mind the chances of a collison are equal to 1 in 2 to the size of the hash we are using, i.e. pretty damned remote.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5ATB1pXyM95IyRhURAnLFAJ48QF9eoqiEHDATpL0iTFToo4Ga3gCfezyt D5FRLPc7imH7Tf6gKkes3nk= =fBQG -----END PGP SIGNATURE----- _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
