Re: Locking in a versioning server
Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Wed, 3 Nov 1999 22:12:07 -0500
Date: Wed, 3 Nov 1999 22:12:07 -0500
Message-Id: <9911040312.AA29983@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <8525680F.0062699C.00@D51MTA03.pok.ibm.com> (ccjason@us.ibm.com)
Subject: Re: Locking in a versioning server
From: ccjason@us.ibm.com
<jra>
Locking an activity prevents any principal other than the owner of the
lock from making any further changes in the context of that
activity. That is, it is not possible to checkout a resource using a
locked activity.
</jra>
Sanity check. Activities are resources, right?
Yes.
Activities can be created (and destroyed?)
Yes. Some servers will probably prevent you from destroying an activity
unless its DAV:revisions collection is empty.
but the activity itself can never be directly modified by client
methods like PROPPATCH, right?
Some servers will allow you to modify the DAV:revisions of an activity
(although the spec currently marks that as readonly ... need to fix that).
Also, you can modify any the dead property on the activity.
(Sorry if it's a dumb question. I only have
the spec to go by.)
I assume there's an implicit smiley face on that (:-).
It looks like required-activites might be user
modifiable... but then again, perhaps it's only set when the activity is
created.
Any property that is not explicitly marked as readonly is writeable.
So DAV:required-activities is writeable.
<jra>
Locking a working resource prevents any principal other than the owner
of the lock from making any change to that working resource. This is
useful in cases where multiple principals share the same workspace,
especially the default workspace.
</jra>
Ah... so one would have to check out a resource and then lock the working
resource if they wanted to lock a resource within their workspace... but not
impact folks working outside their workspace.
Yes.
Cheers,
Geoff