You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by ChadDavis <ch...@gmail.com> on 2010/04/10 00:21:43 UTC
use case for checked-out
I understand how the checkin() and the checked-out property work. But
I'm a bit confused on the use case. For instance, I'm creating a
simple content management system. This system support version
control. When I commit a version of document, the document node is
then left in the check-out=false state, rendering it read only. When
I later edit the document, and save those edits, I checkout the
document node prior to saving my changes. All is understood.
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 . . .
Re: use case for checked-out
Posted by ChadDavis <ch...@gmail.com>.
On Wed, Apr 14, 2010 at 7:02 AM, Alexander Klimetschek <ak...@day.com> wrote:
> On Sat, Apr 10, 2010 at 00:21, ChadDavis <ch...@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?
Re: use case for checked-out
Posted by Alexander Klimetschek <ak...@day.com>.
On Sat, Apr 10, 2010 at 00:21, ChadDavis <ch...@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.
Regards,
Alex
--
Alexander Klimetschek
alexander.klimetschek@day.com