On Tue, 21 Dec 2004, Helge Jensen wrote:
> kfogel@collab.net wrote:
>
> > Specifically, for certain common non-ASCII characters
> > (e.g., most of those representable in ISO-8859-*), we could use an
> > encoding that reads more intuitively to a human:
> >
> > foo/bör/baz.c ==> foo/bor/baz.c
> >
> > or
> >
> > foo/bör/baz.c ==> foo/boer/baz.c
> >
> > This would make the lock tree more debuggable in common cases.
>
> Here, both "foo/bör" and "foo/boer" would translate to the same lock-path.
>
> Basically transformed self-representation needs some escape mechanism no
> matter how you twist and turn it.
>
> This is a built-in problem of variation A.
>
>
In this whole proposal, the filename used in the locking directory is
treated like a hash code in a hash table, so this is just a hash
collision. Then we just store multiple lock entries in the same file. This
isn't specific to variation A, since using just a part of the MD5 hash
increases the risk for collisions.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 21 23:31:52 2004