Next message: by way of : "[Moderator Action] draft-ietf-deltav-versioning-04.8"
Date: Sat, 24 Jun 2000 22:01:23 -0400 (EDT)
Message-Id: <200006250201.WAA01138@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Versioning TeleConf Agenda, 6/5/00 (Monday) 2pm-3pm EST
From: jamsden@us.ibm.com
... The group agreed that is appropriate for LOCK/UNLOCK to
disallow the Target-Selector or Workspace headers.
<jra> Yet more special cases for LOCK and UNLOCK. Could you
enumerate the issues this resolves? I some sense it complicates the
protocol by requiring special handling of locking methods. </jra>
I still need to get minutes out from this weeks call. In particular,
Chris suggested we modify this statement to just say that the behavior
of LOCK/UNLOCK is undefined in the presence of a Target-Selector header.
This keeps the protocol simple, and allows us to defer deciding on
Target-Selector locking semantics until we have more experience with
the protocol.
Cheers,
Geoff