Re: [ietf-caldav] draft-daboo-webdav-sync-01

Roberto Polli <rpolli@babel.it> Wed, 11 March 2009 12:14 UTC

Return-Path: <rpolli@babel.it>
X-Original-To: ietf-caldav@osafoundation.org
Delivered-To: ietf-caldav@osafoundation.org
Received: from localhost (localhost [127.0.0.1]) by leka.osafoundation.org (Postfix) with ESMTP id 70AD37841F7 for <ietf-caldav@osafoundation.org>; Wed, 11 Mar 2009 05:14:45 -0700 (PDT)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Score: -1.642
X-Spam-Level:
X-Spam-Status: No, score=-1.642 tagged_above=-50 required=4 tests=[AWL=0.857, BAYES_00=-2.599, RDNS_DYNAMIC=0.1]
Received: from leka.osafoundation.org ([127.0.0.1]) by localhost (leka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e4VUXKPsmZYE for <ietf-caldav@osafoundation.org>; Wed, 11 Mar 2009 05:14:44 -0700 (PDT)
Received: from postalo2.babel.it (81-208-88-105.ip.fastwebnet.it [81.208.88.105]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by leka.osafoundation.org (Postfix) with ESMTP id 527E57841ED for <ietf-caldav@osafoundation.org>; Wed, 11 Mar 2009 05:14:44 -0700 (PDT)
Received: by postalo2.babel.it (Postfix, from userid 8) id 6CD4D11C616; Wed, 11 Mar 2009 13:14:39 +0100 (CET)
Received: from ananke.localnet (ananke.dhcp.babel.it [10.0.10.215]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: rpolli) by postalo2.babel.it (Postfix) with ESMTP id 4558611C5F6; Wed, 11 Mar 2009 13:14:37 +0100 (CET)
From: Roberto Polli <rpolli@babel.it>
Organization: Babel s.r.l
To: ietf-caldav@osafoundation.org
Date: Wed, 11 Mar 2009 13:14:38 +0100
User-Agent: KMail/1.11.0 (Linux/2.6.24-21-generic; KDE/4.2.0; i686; ; )
References: <29696E9E8589A72FC19EB4F6@caldav.corp.apple.com> <200903101539.33711.rpolli@babel.it> <8F0CB26631865CED16D04B54@caldav.corp.apple.com>
In-Reply-To: <8F0CB26631865CED16D04B54@caldav.corp.apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200903111314.39176.rpolli@babel.it>
Subject: Re: [ietf-caldav] draft-daboo-webdav-sync-01
X-BeenThere: ietf-caldav@osafoundation.org
X-Mailman-Version: 2.1.9
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: Wed, 11 Mar 2009 12:14:45 -0000

On martedì 10 marzo 2009 15:50:29 you wrote:
> Note that the current spec is a generic webdav spec.
you mean the target is about fasten webdav sync and not caldav one?

> You want to get deleted items separately from other changes?
yes. I know the issue is quite complex. Afaik sync process needs at least 3 
methods:
1- get new items since last sync
2- get updated items since last sync
3- get deleted items since last sync

> For CalDAV we would
> need to write an extension that would allow a time-range to be included in
> the report
I miss the point:
* as of now we can find events by time-range with caldav for queries 1) and 2) 
using CREATED|LAST-MOD
* as we lack a method for 3) we're forced to use etags mapping (and storing a 
table on database with a history between syncs), thus retrieving all events 
and retrieve deleted items by difference of sets (stored - retrieved).
* retrieving deleted items directly from server will (partially) solve that 
issue.. 

I wish this mail is not too confuse.

Hope it helps+Peace,
R.

-- 

Roberto Polli
Babel S.r.l. - http://www.babel.it
Tel. +39.06.91801075 - fax +39.06.91612446
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."