- From: Greg Stein <gstein@lyra.org>
- Date: Fri, 1 Dec 2000 21:15:20 -0800
- To: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
- Cc: ietf-dav-versioning@w3.org
On Fri, Dec 01, 2000 at 03:10:51PM -0500, Geoffrey M. Clemm wrote:
>...
> - CHECKIN of an activity (Greg)
>
> This just provides a shorthand for checking in all the checked out
> resources associated with that activity. It appears that the only
> benefit is in decreasing the number of round trips. If anyone
> believes there is a semantic benefit to this operation, please
> explain it to the list.
It is not about decreasing round trips... not a bit. It is about
establishing a change set. All of the changes get checked in as a single
unit and assigned a version number.
I see no way to do a change set if the resources must be checked in
individually. Not to mention the transactional problems with that. For
example, if checkout-fork is true ("allow multiple checkouts"), but
checkin-fork is false ("can't check in if the checked out version is not the
latest"), then I need to cancel the *entire* checkin if *any* of the
checkins would create a fork.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Received on Saturday, 2 December 2000 00:13:18 UTC