Re: Do lock tokens need to be unique?

Karl Fogel wrote:
> Is it strictly necessary that we guarantee the uniqueness of lock tokens?
>
> For more context, see this thread:
>
> "[PATCH] allow pre-lock hook to specify token for locking"
> http://subversion.tigris.org/servlets/BrowseList?list=dev&by=thread&from=667592
>
> It's only six messages long (right now, anyway). We're trying to figure
> out if losing the guarantee that lock tokens are unique would cause any
> badness in the real world. Note cmpilato's post in the thread about how
> it's a WebDAV spec issue. He points to this:
>
> http://www.webdav.org/specs/rfc2518.html#rfc.section.6.3

...better to point to...
<http://www.webdav.org/specs/rfc4918.html#rfc.section.6.5>:

> Lock token URIs MUST be unique across all resources for all time. This uniqueness constraint allows lock tokens to be submitted across resources and servers without fear of confusion. Since lock tokens are unique, a client MAY submit a lock token in an If header on a resource other than the one that returned it.

That being said, I don't believe that anything catastrophic will happen
if there'd be a conflict.

But then: is it really so hard to generate a unique token? After all,
that's why the WebDAV spec recommends using UUID based tokens...

> ...

BR, Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-22 21:11:06 CEST