Re: WebDAv collection sync: last issue
Roberto Polli <[email protected]> Tue, 8 Jun 2010 11:15:47 +0200
| Newsgroups | gmane.ietf.caldav,gmane.ietf.webdav |
|---|---|
| Organization | Babel s.r.l |
| Message-ID | <[email protected]> |
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."