[locking] out-of-dateness checking during lock

Hi,

I'm starting to design the locking API in svn_client. I presume nobody
else is doing that, please tell me otherwise. The main motivation is that
I want to test ra_svn and that's simpler if we have client support, even
if not complete.

ONe thing I'm not sure about is the out-of-date checking when locking the
path. It is stated in the locking UI design that a path must be up-to-date
when locked. I assume we want to do this atomically.

The current RA API lock function doesn't allow the client to provide a
revision number. We can ask the server for last committed revision of the
path, but that wouldn't atomic. Maybe someone has a plan for how to deal
with this. sussman? fitz?

Regards,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 4 14:30:25 2004