postcondition for PUT

From: Boris Bokowski/OTT/OTI (Boris_Bokowski@oti.com)
Date: Thu, Aug 17 2000

  • Next message: Boris Bokowski/OTT/OTI: "are workspaces versionable?" 

    To: ietf-dav-versioning@w3.org
Message-ID: <OF1D2F5513.4C0D7288-ON8525693E.006941C1@ott.oti.com>
From: "Boris Bokowski/OTT/OTI" <Boris_Bokowski@oti.com>
Date: Thu, 17 Aug 2000 15:20:04 -0400
Subject: postcondition for PUT

Hi,

I have some small questions with respect to the 07 draft. For the first 
question, see below.
I'll send separate mails for the other questions.

First question, regarding 5.4: "If the PUT creates a new resource, it is 
server defined whether it is under version control."

     If a server chooses to put files under version control automatically, 
what is the effect of a PUT? Does this create a 
     new history resource, a new version (implicit CHECKIN...) in that 
history resource, and a version selector at the request 
     URL which selects the new version?
     A subsequent PROPPATCH, issued by a client before issuing 
VERSION-CONTROL, would fail in this case. Therefore, 
     a client would have to issue a PROPFIND on the newly created resource 
first, to find out whether it is a version selector 
     or not.
     The same applies to versioned collections (12.6)

Thanks, Boris.