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

Problems with Delete of a version-controlled collection

From: Kirmse, Daniel <daniel.kirmse@sap.com>
Date: Wed, 16 Jan 2002 17:13:40 +0100
Message-ID: <59357A260E15D311B5A60008C75D3530068B4767@dbwdfx13.wdf.sap-ag.de>
To: "Ietf-Dav-Versioning (E-mail)" <ietf-dav-versioning@w3.org>
Hi,

suppose this:

	/foo
        |
        +- /bar
             |
             +- foobar.c

all the resources are under version-control. Now suppose this sequence of
requests:

CHECKOUT /foo/bar
  DAV:apply-to-version

(working-collection: /wc/wc1  auto-update: /foo/bar)

CHECKOUT /foo
  DAV:apply-to-version

(working-collection: /wc/wc2, auto-update: /foo)

delete folder /foo/bar:
DELETE /wc/wc2/bar   
or is it done via the real VCR? I hope not! The DELETE should be hidden
until checkin!

CHECKIN /wc/wc2
(applied to /foo -> the folder /bar and all its content is gone)

CHECKIN /wc/wc1
(must fail because the VCR the auto-update should go to is gone)


Questions:
1. Is this right?
2. If yes: Shouldn't the deletion be prevented or fail because a subfolder
is checked out and therefore some kind of "locked"?


Regards,
Daniel
Received on Wednesday, 16 January 2002 11:33:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:43 GMT