W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2005

Re: [Ietf-caldav] [Fwd: draft-reschke-http-addmember-00]

From: Lisa Dusseault <lisa@osafoundation.org>
Date: Thu, 17 Feb 2005 13:42:21 -0800
Message-Id: <b379cf31de8e1092e8395b74181c0911@osafoundation.org>
Cc: "'Julian Reschke'" <julian.reschke@gmx.de>, "'Webdav WG'" <w3c-dist-auth@w3c.org>
To: <ejw@soe.ucsc.edu>

Rather than a new method, an ADDMEMBER specification could require 
support for the Expect mechanism which solves that problem rather 
neatly for any method.


On Feb 17, 2005, at 1:04 PM, Jim Whitehead wrote:

> A few comments on extending the functionality defined in -addmember-00:
> 1) One problem clients currently encounter with PUT is determining 
> whether
> they have permission to write to a specific location. At present, a 
> client
> must submit a PUT (or ADDMEMBER) with the entire entity body, then 
> wait for
> the response, or the authentication challenge. It would be very nice 
> to have
> a TESTPUT/TESTADDMEMBER method that sees whether a write (via PUT or
> ADDMEMBER) would succeed, or if an authentication challenge is needed.
> Yes, a server supporting ACLs could be queries to see if writing were
> allowed, but it still doesn't provide an easy way to pre-determine the
> authentication information.
> 2) It would be very helpful to allow ADDMEMBER to have atomic 
> capabilities, to write both the resource and its metadata in one 
> action.
> - Jim
Received on Thursday, 17 February 2005 21:44:24 UTC

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