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

RE: Activities

From: Kirmse, Daniel <daniel.kirmse@sap.com>
Date: Mon, 14 Jan 2002 17:21:39 +0100
Message-ID: <59357A260E15D311B5A60008C75D3530068B4751@dbwdfx13.wdf.sap-ag.de>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>

right the DAV:one-checkout-per-activity-per-history precondition (Sec.13.10)
does it for two VCR's pointing to the very same version-history. My problem
was more general. I want to prevent any two VCR's of two workspaces (VCR1
member of WS1 and VCR2 member of WS2) to be in the same activity. So
changing VCR's of both of the workspaces I do need two activities. One for
each Workspace.

Background: I want to prevent a client mixing up changes made to a
development codeline and changes made to a correction or consolidation
codeline into one activity.

As you said for VCR's sharing the same version-history this is ensured with
the precondition you mentioned. It is for the other ones I need a solution
for. Thats why I came up with the idea of restricting the
DAV:current-workspace-set property to contain at most one workspace


>-----Original Message-----
>From: Tim Ellison [mailto:Tim_Ellison@uk.ibm.com]
>Sent: Montag, 14. Januar 2002 16:27
>To: ietf-dav-versioning@w3.org
>Subject: RE: Activities
>"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 11:22:13 UTC

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