IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Tue, 22 February 2005 20:02 UTC

X-Envelope-From: julian.reschke@gmx.de
X-Envelope-To: <ietf-caldav@osafoundation.org>
Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by kahuna.osafoundation.org (8.12.8/8.12.8) with SMTP id j1MK29aZ009130 for <ietf-caldav@osafoundation.org>; Tue, 22 Feb 2005 12:02:09 -0800
Received: (qmail invoked by alias); 22 Feb 2005 20:02:03 -0000
Received: from pD9E62405.dip.t-dialin.net (EHLO [192.168.0.3]) (217.230.36.5) by mail.gmx.net (mp018) with SMTP; 22 Feb 2005 21:02:03 +0100
X-Authenticated: #1915285
Message-ID: <421B8FB3.6050102@gmx.de>
Date: Tue, 22 Feb 2005 21:01:55 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Roy T. Fielding" <fielding@gbiv.com>
Subject: Re: [Ietf-caldav] [Fwd: draft-reschke-http-addmember-00]
References: <4214D227.9020607@gmx.de> <1108663634.11773.28.camel@sukothai.pingtel.com> <4214E4D0.80408@gmx.de> <1108670449.11773.33.camel@sukothai.pingtel.com> <4214F973.9060404@gmx.de> <1109017914.3811.29.camel@localhost.localdomain> <20050221212838.GA8870@mail.shareable.org> <1109040989.3811.39.camel@localhost.localdomain> <20050222034655.GC4504@markbaker.ca> <7d6e31bc68586bba82b76fd4fe4443ba@gbiv.com> <20050222133758.GD4504@markbaker.ca> <c126af63ffe0c6f778badbaf438ca38c@gbiv.com>
In-Reply-To: <c126af63ffe0c6f778badbaf438ca38c@gbiv.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0 ()
X-Scanned-By: MIMEDefang 2.48 on 127.0.0.1
Cc: Mark Baker <distobj@acm.org>, WebDAV WG <w3c-dist-auth@w3.org>, HTTP Working Group <ietf-http-wg@w3.org>, CalDAV DevList <ietf-caldav@osafoundation.org>
X-BeenThere: ietf-caldav@osafoundation.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Discussions on Calendar Access protocol based on WebDAV <ietf-caldav.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-caldav>, <mailto:ietf-caldav-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-caldav>
List-Post: <mailto:ietf-caldav@osafoundation.org>
List-Help: <mailto:ietf-caldav-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-caldav>, <mailto:ietf-caldav-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2005 20:02:10 -0000

Roy T. Fielding wrote:
> 
> On Feb 22, 2005, at 5:37 AM, Mark Baker wrote:
> 
>> Ah, so you're saying that ADDMEMBER isn't uniform?
> 
> 
> Actually, no, I was saying that ADDMEMBER as currently defined
> is identical to POST.  Julian said that it wasn't identical because
> his client would be able to expect one semantic, namely that a
> 201 result would cause the webdav collection to contain a new
> member with the given media type.  That implies an additional
> requirement that the target be a webdav collection, which isn't
> uniform at all.

I'm not sure how you get to that conclusion. ADDMEMBER (as proposed) 
doesn't require the target resouce to be a WebDAV collection.

> ...

Best regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

v2.23.0 | Report a Bug | By Email