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

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

X-Envelope-From: julian.reschke@gmx.de
X-Envelope-To: <ietf-caldav@osafoundation.org>
Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by kahuna.osafoundation.org (8.12.8/8.12.8) with SMTP id j1MJO7aZ004222 for <ietf-caldav@osafoundation.org>; Tue, 22 Feb 2005 11:24:07 -0800
Received: (qmail invoked by alias); 22 Feb 2005 19:24:00 -0000
Received: from pD9E62405.dip.t-dialin.net (EHLO [192.168.0.3]) (217.230.36.5) by mail.gmx.net (mp015) with SMTP; 22 Feb 2005 20:24:00 +0100
X-Authenticated: #1915285
Message-ID: <421B86CC.7020402@gmx.de>
Date: Tue, 22 Feb 2005 20:23:56 +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: Jamie Lokier <jamie@shareable.org>
References: <d23b29d789b472835a75d0b2038b6ba0@gbiv.com> <OF5A5B41F6.0D254554-ON85256FAC.00181251-85256FAC.001C76B8@us.ibm.com> <20050221213247.GB8870@mail.shareable.org> <421B6778.1080804@gmx.de> <20050222190228.GD22555@mail.shareable.org>
In-Reply-To: <20050222190228.GD22555@mail.shareable.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.05 () FORGED_RCVD_HELO
X-Scanned-By: MIMEDefang 2.48 on 127.0.0.1
Cc: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>, HTTP Working Group <ietf-http-wg@w3.org>, WebDAV <w3c-dist-auth@w3.org>, CalDAV DevList <ietf-caldav@osafoundation.org>
Subject: [Ietf-caldav] Re: draft-reschke-http-addmember-00
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 19:24:08 -0000

Jamie Lokier wrote:
> Julian Reschke wrote:
> 
>>I'm not sure what your point is. Of course if a server mishaves that 
>>way, a client accessing it may cause problems. But that's the problem of 
>>the server, and I don't think there's anything we can do about that when 
>>discussing HTTP based protocols.
>>
>>What am I missing?
> 
> 
> You're missing that when you are doing CalDAV* requests, you _know_ the
> URL you are accessing is CalDAV compliant already.  (* - example).

How does a client do *any* kind of server feature discovery if *any* 
method (including things like OPTIONS) may cause harm because of broken 
server implementations?

> If you don't know that you have big problems.

Such as?

> So you don't need new methods just to express "intent".
> (Maybe for other reasons, but not this one).

Best regards, Julian

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