Next message: Clemm, Geoff: "RE: Locking a workspace"
To: ietf-dav-versioning@w3.org
Message-ID: <OF25507C0A.682383FD-ON852568EF.00524AC1@ott.oti.com>
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Date: Tue, 30 May 2000 11:01:43 -0400
Subject: Re: Locking a workspace
I did not take from the proposal that the target selection criteria for a
workspace would be manifested as members of the workspace 'collection'.
Rather that the workspace contained resources that were selected in a
'higher priority' to the 'global' resources.
If the target selections are collection members, the workspace collection
would not have a dav-compliant namespace.
Tim
"Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
Sent by: ietf-dav-versioning-request@w3.org
29-05-00 10:56 PM
To: ietf-dav-versioning@w3.org
cc:
Subject: Re: Locking a workspace
With the proposed "workspace is a collection" semantics, you can
get such a lock by issuing a depth lock against the workspace collection.
I guess this is another benefit of the "workspace as collection" approach.
Cheers,
Geoff
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Date: Mon, 29 May 2000 16:51:51 -0400
Is there any mechanism for preventing others from issuing a set-target
against a workspace (so that it always selects the same thing)?
How about locking the workspace (although the selection criteria are
neither content nor properties)?
Tim