Re: draft of CHECKOUT method
Jim Whitehead (ejw@ics.uci.edu)
Tue, 12 Oct 1999 16:06:26 -0700
From: Jim Whitehead <ejw@ics.uci.edu>
To: ietf-dav-versioning@w3.org
Date: Tue, 12 Oct 1999 16:06:26 -0700
Message-ID: <NDBBIKLAGLCOPGKGADOJIEIKCGAA.ejw@ics.uci.edu>
In-Reply-To: <F3B2A0DB2FC1D211A511006097FFDDF534389E@BEAVMAIL>
Subject: RE: draft of CHECKOUT method
One thought I had on CHECKOUT today is that I think we want CHECKOUT to
return a list of other working resources that are currently active and were
also created by a checkout against the same parent. An authoring client
would use this information to inform a user that they are about to enter a
parallel development/authoring situation, and give them the option to not
continue if they do not wish to merge.
While a client could query for this before performing the checkout, there's
no guarantee someone else wouldn't sneak in a checkout between the query and
the following checkout, thus making the query result out-of-date.
Thoughts?
- Jim
> Here is my first draft of the CHECKOUT method. There are more
> details that
> need to be nailed down, especially WRT CHECKOUT of collections,
> but I wanted
> to get this out for some feedback.
>
> <<bhscheckout.doc>>
> --Sarge
>
>