Generally speaking the generation of a hash value for an entity won't always be unique. Of course most hash table implementations get around this issue using such techniques as chaining. However, what that has to do with my email I don't know. The technique I described and the code I shared specifically creates keys that are in sequence avoiding any collisions.

-Matt

On Tuesday, June 17, 2003, at 02:54 AM, Sean A Corfield wrote:

On Monday, Jun 16, 2003, at 23:41 US/Pacific, Matt Liotta wrote:
Where is the potential collision? Each node is added in sequence to the tree and its hash reflects that sequence.

Entity -> hash is not a 1:1 mapping. Some entities will map to the same hash.


Sean A Corfield -- http://www.corfield.org/blog/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood

----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.


CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.


CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).

Reply via email to