W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2002

RE: GULP (version 4)

From: Lisa Dusseault <lisa@xythos.com>
Date: Thu, 10 Oct 2002 10:19:33 -0700
To: "'Julian Reschke'" <julian.reschke@gmx.de>, "'Clemm, Geoff'" <gclemm@rational.com>, "'Webdav WG'" <w3c-dist-auth@w3c.org>
Message-ID: <000001c27081$33e6a1c0$b701a8c0@xythoslap>

> "If a request would modify the state of a resource, the request MUST
> unless the lock-token for that lock is specified in the request."

This isn't much more specific than the current "is affected by"
language.  It leaves it entirely up to the server to decide what
modifying the state of a resource is.  Does modifying membership count?
(Is modifying membership blocked by a depth 0 lock?)  Does modifying
property values count?

This is exactly where clients have had problems submitting simple
requests to server implementations that each have a different idea what
resources have state modified by the request.

Received on Thursday, 10 October 2002 14:10:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:27 UTC