W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2002

RE: Activities

From: Tim Ellison <Tim_Ellison@uk.ibm.com>
Date: Mon, 14 Jan 2002 15:26:32 +0000
To: ietf-dav-versioning@w3.org
Message-ID: <OFA76C8070.92D35F27-ON80256B41.00530950@portsmouth.uk.ibm.com>
"Kirmse, Daniel" <daniel.kirmse@sap.com> wrote:

> Would it be acceptable to have server with the following
> behavior:
> A client performs a checkout to a VCR located within a
> certain workspace WS to some activity not containing any
> versions yet. Regarding to this the DAV:current-workspace-set
> property must be empty.  After the checkout the
> DAV:current-workspace-set property contains a href of WS.
> Now the server is implemented that way that
> DAV:current-workspace-set does contain one workspace at most.
> Given that a checkout to a VCR located within a different
> workspace WS' to the very same activity must fail.
> With that an activity is only able to contain versions of
> resources of one workspace only.

I think it would be simpler to create a new activity, let's say 
/foo/unique, then do all the subsequent check-outs with a request body 
including an activity set, but not including unreserved, i.e., 
<DAV:checkout> <DAV:activity-set> 
<DAV:href>http://bar/foo/unique</DAV:href> </DAV:activity-set> 
</DAV:checkout>. The DAV:one-checkout-per-activity-per-history 
precondition (Sec.13.10) should do it.

Received on Monday, 14 January 2002 10:36:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:48 UTC