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

RE: Localisation header on creating a new version

From: Clemm, Geoff <gclemm@rational.com>
Date: Mon, 7 Jan 2002 22:05:16 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B10557733C@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
The rationale for having CHECKIN return a Location header was that
the "primary purpose" of the CHECKIN request is to create a new 
resource (i.e. a new version resource), while the "primary purpose" of
a VERSION-CONTROL request is to put an existing resource under
version control (and the creation of a version and a
version history was merely a side effect).

But this rationale is not nearly as compelling as something like
CHECKOUT returning the location of a new working resource in the
Location header, in which case unlike CHECKIN, you don't have
any other good way to find the URL of the resource you just created.

So the use of the Location header in CHECKIN is probably best thought
of as a historical quirk.


-----Original Message-----
From: Edgar@EdgarSchwarz.de [mailto:Edgar@EdgarSchwarz.de]
Sent: Monday, January 07, 2002 5:01 PM
To: ietf-dav-versioning@w3.org
Cc: Edgar@EdgarSchwarz.de
Subject: Localisation header on creating a new version

if I read the spec correctly on creation of a new (initial) version by
the version URL must be accessed by DAV:checked-in of the new VCR.
Using CHECKIN to create an additional version returns the version URL in a
header. BTW, I guess that a CHECKIN on a baseline also returns the baseline
So why don't we return a Location header with VERSION-CONTROL and
if a new version/baseline was created ?
Received on Monday, 7 January 2002 22:45:13 UTC

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