Re: [caldav] WebDAv collection sync: last issue

Roberto Polli <rpolli@babel.it> Tue, 08 June 2010 09:15 UTC

Return-Path: <rpolli@babel.it>
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 E9CB93A69A8; Tue, 8 Jun 2010 02:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.081
X-Spam-Level: ***
X-Spam-Status: No, score=3.081 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_13=0.6, J_CHICKENPOX_55=0.6]
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 y3u1+nkp5Qkk; Tue, 8 Jun 2010 02:15:33 -0700 (PDT)
Received: from smtp.babel.it (ns1.babel.it [89.97.242.210]) by core3.amsl.com (Postfix) with ESMTP id 81FE828C149; Tue, 8 Jun 2010 02:15:30 -0700 (PDT)
Received: from smtp.babel.it (localhost [127.0.0.1]) by smtp.babel.it (Postfix) with ESMTP id 6910B4D492; Tue, 8 Jun 2010 11:15:26 +0200 (CEST)
Received: from rpolli.localnet (rpolli.dhcp.babel.it [10.0.10.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: rpolli) by smtp.babel.it (Postfix) with ESMTPSA id 3F5FE4D478; Tue, 8 Jun 2010 11:15:26 +0200 (CEST)
From: Roberto Polli <rpolli@babel.it>
Organization: Babel s.r.l
To: caldav@ietf.org
Date: Tue, 8 Jun 2010 11:15:47 +0200
User-Agent: KMail/1.12.2 (Linux/2.6.31-21-generic; KDE/4.3.2; i686; ; )
References: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com>
In-Reply-To: <2D7356DA1153057D7AE554D8@caldav.corp.apple.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201006081115.47308.rpolli@babel.it>
X-AV-Checked: ClamAV using ClamSMTP
Cc: w3c-dist-auth@w3.org, vcarddav@ietf.org
Subject: Re: [caldav] WebDAv collection sync: last issue
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: Tue, 08 Jun 2010 09:15:55 -0000

On Monday 07 June 2010 15:57:09 Cyrus Daboo wrote:
> The question is whether collection resources that are immediate children of
> the collection being targeted for the REPORT should be reported as
> "modified" if any of their child resources (depth infinity) are modified.
aware of the performance issue, I think that the right behavior should be 
depth: infinity.

while the performance issue should be solved by the storage layer (eg. 
filesystem or database, which perform that op quite nicely)
and while the average depth level rarely goes above 4 (and in most cases it's 
3 or 2) 

Having depth:1 can be confusing, as that feature is supposed to notify whether 
I have to sync or not a given folder.

My 2 cents+Peace,
R.

-- 

Roberto Polli
Babel S.r.l. - http://www.babel.it
Tel. +39.06.91801075 - fax +39.06.91612446
Tel. cel +39.340.6522736
P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma)

"Il seguente messaggio contiene informazioni riservate. Qualora questo 
messaggio fosse da Voi ricevuto per errore, Vogliate cortesemente darcene 
notizia a mezzo e-mail. Vi sollecitiamo altresì a distruggere il messaggio 
erroneamente ricevuto. Quanto precede Vi viene chiesto ai fini del rispetto 
della legge in materia di protezione dei dati personali."