Re: Missing advanced preconditions from PUT, MKCOL, COPY?

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

  • Next message: Geoffrey M. Clemm: "Re: Versioning TeleConf Agenda, 8/18/00 (Monday) 2pm-3pm EST"

    Date: Mon, 18 Sep 2000 12:49:49 -0400 (EDT)
    Message-Id: <200009181649.MAA14367@tantalum.atria.com>
    From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
    To: ietf-dav-versioning@w3.org
    Subject: Re: Missing advanced preconditions from PUT, MKCOL, COPY?
    
    
    Yes, I'll add this.  In particular, I'll say that when a server
    automatically puts under version control any new resource created by
    PUT, MKCOL, and COPY, then all the pre-conditions of VERSION-CONTROL
    must be satisfied by the PUT, MKCOL, or COPY.
    
    Cheers,
    Geoff
    
       From: Tim_Ellison@uk.ibm.com
    
       Yes, that's right.
    
       "Vasta, John" <jvasta@rational.com> on 2000-09-15 06:06:07 PM
    
       With versioned collections, the PUT, MKCOL, and COPY methods can
       cause collections to be automatically modified. Shouldn't the
       advanced versioning section note that
       DAV:cannot-modify-parent-version-selector is an additional
       precondition for PUT and MKCOL, and
       DAV:cannot-modify-destination-parent-version-selector is an
       additional precondition for COPY?