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

Re: Locking UI comments

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-10-14 03:10:13 CEST

Justin Erenkrantz <justin@erenkrantz.com> wrote on 10/13/2004 05:12:50 PM:

> --On Wednesday, October 13, 2004 4:37 PM -0400 Mark Phippard
> <MarkP@softlanding.com> wrote:
>
> > Plus, we have established that you can only lock the youngest revision
> > anyway, or more specifically your WC has to have the youngest
revision.
>
> I think you are restricting yourself to only Subversion as a client. I'm

> purposely thinking of Adobe Photoshop with its integrated WebDAV-aware
> client which supports locking. Photoshop will issue a LOCK on a
resource,
> but it has no concept of a 'youngest' revision. You couldn't even tell
it
> that. However, this is also why most WebDAV clients issue a LOCK then
> issue a GET. This ensures that they get the 'youngest' revision of the
> resource after they acquired the lock. -- justin

Actually, I was considering that. In the WebDAV example, the server is
just going to give the client the correct version. My point was that
since there is nothing in the proposed spec that would allow you to
explicitly or implicitly lock anything other than the latest revision,
there should not be any problem supporting the WebDAV concepts you have
outlined.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 14 03:10:38 2004

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