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

[Roberto Polli <[e-mail]>]

On mercoledì 11 marzo 2009 14:32:24 you wrote:
> this spec applies to both (and to
> any other webdav based protocol e.g. CardDAV).
ok, now all is clear ;) 

> >> For CalDAV we would
> >> need to write an extension that would allow a time-range to be included
> >> in the report
ok. Another way could be returning the sync info in the report query, like 
what we do for the etags - but maybe this is not ok for other DAV protocols (I 
know caldav only)

eg for calendar-query: REPORT /my/dav/path
<D:calendar-query>
<D:prop>
       <D:getetag/>
       <D:sync-token>1234</D:sync-token>
</D:prop>
<D:filter>
....
</D:filter>
</D:calendar-query>


I should add the <D:sync-token>5678</D:sync-token> in the response.
A drawback is that we should return the same sync token in each multi-status 
stanza.


> > ... using CREATED|LAST-MOD
> Hmm, this is rather dangerous since those iCalendar properties are
> controlled by the client, not by the server.
I'm not sure caldav servers take dumbly these props from client. I hope to 
find some time to go in depth about it.


> I think the current spec returns exactly what you want.
except for the time-range issue, they seems ok.


Thank you very much for your response!

Peace, R.

-- 

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