jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ChadDavis <chadmichaelda...@gmail.com>
Subject Re: use case for checked-out
Date Wed, 14 Apr 2010 15:22:37 GMT
On Wed, Apr 14, 2010 at 7:02 AM, Alexander Klimetschek <aklimets@day.com> wrote:
> On Sat, Apr 10, 2010 at 00:21, ChadDavis <chadmichaeldavis@gmail.com> wrote:
>> However, I'm unclear about what the purpose of the read-only checked
>> out status is?  Perhaps it doesn't necessarily provide anything to my
>> simple system, but I'm interested in what cases this is useful . . .
> Citing the spec (2.0, section 15.3):
> The checked-out state indicates to the repository and other clients
> that the latest version of N is “being worked on” and will typically
> be checked-in again at some point in the future, thus creating a new
> version.

Yes.  I have read the specification.  But what I would like to hear is
how people use it in their applications.  I'm guessing it's something
like checking the checked-out property before allowing a user to edit
a document, and if it's check-out not letting them open it, unless in
read only?

View raw message