Re: [caldav] Retry request status
Mike Douglass <douglm@rpi.edu> Fri, 12 March 2010 19:22 UTC
Return-Path: <douglm@rpi.edu>
X-Original-To: caldav@core3.amsl.com
Delivered-To: caldav@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90C703A69D8 for <caldav@core3.amsl.com>; Fri, 12 Mar 2010 11:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wbT7ITKQUO3L for <caldav@core3.amsl.com>; Fri, 12 Mar 2010 11:22:05 -0800 (PST)
Received: from smtp5.server.rpi.edu (smtp5.server.rpi.edu [128.113.2.225]) by core3.amsl.com (Postfix) with ESMTP id B965B3A6993 for <caldav@ietf.org>; Fri, 12 Mar 2010 11:21:10 -0800 (PST)
Received: from [128.113.124.235] (kiva-07.dynamic2.rpi.edu [128.113.124.235]) (authenticated bits=0) by smtp5.server.rpi.edu (8.13.1/8.13.1) with ESMTP id o2CJL4Do012600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Mar 2010 14:21:04 -0500
Message-ID: <4B9A9420.5070509@rpi.edu>
Date: Fri, 12 Mar 2010 14:21:04 -0500
From: Mike Douglass <douglm@rpi.edu>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Tim Olsen <tim@brooklynpenguin.com>
References: <4B9A905A.2060804@rpi.edu> <4B9A933A.80308@brooklynpenguin.com>
In-Reply-To: <4B9A933A.80308@brooklynpenguin.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-RPI-SA-Score: undef - SENDER Whitelisted (douglm@rpi.edu: Mail from user authenticated via SMTP AUTH allowed always)
X-CanItPRO-Stream: outgoing
X-Canit-Stats-ID: Bayes signature not available
X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.225
Cc: caldav@ietf.org
Subject: Re: [caldav] Retry request status
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2010 19:22:06 -0000
I looked at that as well: conflict seemed to carry the sense of what was happening: I''d be happy with either though Tim Olsen wrote: > Mike Douglass wrote: > >> I'm thinking of a 409 response with an error response like <DAV:retry/> >> > > I recommend a 503 with a Retry-After header. See > http://www.greenbytes.de/tech/webdav/rfc2616.html#status.503 > > Tim > > -- Mike Douglass douglm@rpi.edu Senior Systems Programmer Communication & Collaboration Technologies 518 276 6780(voice) 2809 (fax) Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180
- [caldav] Retry request status Mike Douglass
- Re: [caldav] Retry request status Tim Olsen
- Re: [caldav] Retry request status Mike Douglass
- Re: [caldav] Retry request status Cyrus Daboo
- Re: [caldav] Retry request status Mike Douglass