Re: Locking a workspace

From: Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Date: Mon, May 29 2000

  • Next message: Geoffrey M. Clemm: "Re: If: header and "parent" resource checking"

    Date: Mon, 29 May 2000 22:56:02 -0400 (EDT)
    Message-Id: <200005300256.WAA22979@tantalum.atria.com>
    From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
    To: ietf-dav-versioning@w3.org
    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