-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 K. Richard Pixley wrote: > Jon Bright wrote: >> K. Richard Pixley wrote: >>> You do nothing. It's up to the administrator of bar.com to resolve >>> this collision. Only one of you is actually authorized to use this >>> name. Repository name doesn't necessarily change with IP or domain >>> name change. >> >> OK, but let's say I'm foo.bar.com, I'm syncing with someone and >> suddenly a revision appears which is named 1:foo.bar.com - but it's >> not from me..?
Instead of a friendly name, I'd use the developer's pub/priv key? with a friendly name as a label for that key (or simply the email associated with the pub key) (In the land of pure theory, now) I could see a scheme where the revision key is a simple serial unique to a developer, or in other words generated on a per-public-key basis. You still have a chance of collision at the developer-public-key level, but since you're using far fewer randomly-generated keys, your collision chance is low, and it only has to be detected at the transaction level, not for each ID generated. Also, you still need to check for duplicate keys, unless you really trust the remote server. Etc. I'm sure there are many problems with the idea. Just had a thought. I can't help it, my brain keeps on thinking when I want it to stop. :o Regards, tom - -- Tom Surace ) ,~~v~~, [EMAIL PROTECTED] ) ,`. .`, http://www.byteheaven.com ) ------------- === + === --- Hamster was here -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCZXLdDoEO2NB2KMURAtmgAJ0anCXHRptoQPv6JqVom+FY+5IKHgCghoFd rHcKM3qCVHnqXmP9WLLAwFo= =YudC -----END PGP SIGNATURE----- _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel