Applying MERGE to the resource being modified

• From: Clemm, Geoff <gclemm@rational.com>
• Date: Thu, 28 Dec 2000 00:33:51 -0500
• To: "DeltaV (E-mail)" <ietf-dav-versioning@w3.org>
• Message-ID: <3906C56A7BD1F54593344C05BD1374B1018619E4@SUS-MA1IT01>

Currently, the request-URL of the MERGE request identifes the
versions being merged, and a Destination header identifies the
version selectors being updated.  This is probably backwards,
since you want the server that holds the version selectors to
get the request, not the server holding the versions (they might
be on different servers).

So I propose that we swap this around, and have the request-URL
of the MERGE request identify the "merge destination", and identify
the versions to be merged in the MERGE request body.

Any objections?  (Note: no semantic change here, just tweaking
the marshalling).

Cheers,
Geoff

Received on Thursday, 28 December 2000 00:34:29 UTC