Re: Locking a workspace

From: jamsden@us.ibm.com
Date: Mon, May 29 2000

Next message: jamsden@us.ibm.com: "Re: If: header and "parent" resource checking"

Previous message: Tim Ellison/OTT/OTI: "Locking a workspace"
Maybe in reply to: Tim Ellison/OTT/OTI: "Locking a workspace"
Next in thread: Geoffrey M. Clemm: "Re: Locking a workspace"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Other mail archives: [this mailing list] [other W3C mailing lists]
Mail actions: [ respond to this message ] [ mail a new topic ]

From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <852568EE.00814E73.00@d54mta02.raleigh.ibm.com>
Date: Mon, 29 May 2000 19:32:19 -0400
Subject: Re: Locking a workspace

If workspaces are a kind of collection where their members are their target
revisions and working resources, then locking a workspace would make sense
as SET-TARGET updates the members.

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

Next message: jamsden@us.ibm.com: "Re: If: header and "parent" resource checking"
Previous message: Tim Ellison/OTT/OTI: "Locking a workspace"
Maybe in reply to: Tim Ellison/OTT/OTI: "Locking a workspace"
Next in thread: Geoffrey M. Clemm: "Re: Locking a workspace"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Other mail archives: [this mailing list] [other W3C mailing lists]
Mail actions: [ respond to this message ] [ mail a new topic ]