[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r11750 - branches/locking/subversion/include

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2004-11-05 15:45:18 CET

Ben Collins-Sussman wrote:
> 1. check to see if there's a pre-existing lock on the file.
> if not, proceed normally.
> 2. if there's a lock, look at the 'owner' field in the lock. Is it
> the same as the authenticated username? If not, error out.
> 3. [check the lock-token]

I'm not in this conversation, really, but, from a bystander's point of view, it
is not clear why step 2 is needed. Why not just proceed to checking the lock
token, which presumably includes the user name in some plain or implied form,
without first checking the user name explicitly?

- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 5 15:45:53 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.