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: Thu, 10 Jan 2002 17:30:29 +0000
To: ietf-dav-versioning@w3.org
Message-ID: <OFFE3BBB45.1C651316-ON80256B3D.005F4971@portsmouth.uk.ibm.com>

You are right that there is no way to restrict an activity resource only 
to select versions of a single workspace.  Given that all checked-out 
resources (i.e. working-resources as well as checked-out 
version-controlled resources) have an unprotected DAV:activity-set, this 
would be potentially very expensive to enforce -- it would have to be done 
on the proppatch.  DeltaV does not preclude servers from enforcing such a 
rule if you choose to do so. but it is not required by the protocol 


"Kirmse, Daniel" <daniel.kirmse@sap.com>
Sent by: ietf-dav-versioning-request@w3.org
2002-01-10 11:32 AM

        To:     "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
        Subject:        Activities



a question dealing with activities:

Suppose two  workspaces A and B. Both of them are under baseline control 
its own. Now suppose an activity C. Is there a server side mechanism 
in DeltaV that could prevent a client from checking out resources of WS A
and B and including them by the way into activity C. Instead a client 
be forced to checkout a resource of WS B into a different activity if
activity C allready contains a checked out resource of workspace A.

From reading the DeltaV I got no idea how to do this, propably it's not 
there ...

Received on Thursday, 10 January 2002 12:31:48 UTC

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