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

RE: 3.5: VERSION-CONTROL response codes

From: Clemm, Geoff <gclemm@rational.com>
Date: Thu, 10 Oct 2002 11:09:56 -0400
Message-ID: <E4F2D33B98DF7E4880884B9F0E6FDEE2973BB8@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
To date, we've limited 3253 modifications to demonstrable
semantic problems with the protocol (e.g. the Label header)
or interoperability problems (the use of an OPTIONS body).

I personally would not want to modify/extend the protocol
simply for "consistency".  This makes the protocol too much of a
moving target for implementors.

For the same reason, I would not want to modify/extend the
protocol for optimizing certain requests, until it has been demonstrated
that these performance issues are common and severe.

But it certainly would be reasonable to define these extensions in a
separate draft, and add that draft to the list of proposed DeltaV 
extensions on the DeltaV web site.  That way implementors who encounter
these performance issues can work around them in a common way,
making that extension a likely candidate for inclusion in the next
draft.

Cheers,
Geoff 

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@greenbytes.de]
Sent: Thursday, October 10, 2002 4:32 AM
To: ietf-dav-versioning@w3.org
Subject: 3.5: VERSION-CONTROL response codes



Hi.

The VERSION-CONTROL method -- when applied to a versionable but not yet
version-controlled resource, creates one or two new resources (being the
checked-in version and optionall the version history resource).

I'd like to see the definition in 3.5 extended to

- allow a 201 to be returned when new resources were created (see [1])

- define that in this case, the Location header should point to the version
being created

- define an optional response body (DAV:version-control-response) that
contains references to the resources being created, such as:

<version-control-response xmlns="DAV:">
  <checked-in>...</checked-in>
  <version-history>...</version-history>
</version-control-response>

(similar marshalling may also be needed for other methods that create new
resources)


[1] <http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.10.2.2>
--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 10 October 2002 11:10:28 GMT

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