[Ietf-caldav] Truncation of large responses

[Lisa Dusseault]

Actually I once worked on an extension, which worked fine, to request a  
"page" of results at a time.  The server knew what was in the collection  
and had some idea of order so you could ask for results 1 to 40, then 41  
to 80 in a separate request.  There was no guarantee that a new item  
wouldn't slip between the cracks, but then this wasn't intended for  
synchronization -- it was intended for browsing.

I don't think it's required for CalDAV, however, because we've got the  
date-limiting range requests in our reports.

Lisa

On Thu, 14 Jul 2005 11:03:00 -0700, Helge Hess  
<helge.hess at opengroupware.org> wrote:

> On Jul 14, 2005, at 19:56, Mike Douglass wrote:
>> Should there be some other mechanism e.g. give me a 1000 events  
>> starting at the 3000th?
>
> Such an operation probably wouldn't make a lot of sense due to  
> concurrent access on the collection.
>
> What you can do as a client to reduce transfer sizes is to first query  
> minimal information of all records (eg just the etags) and then use  
> batches to retrieve the actual content in steps.
>
> This would probably be the thing being done by offline oriented clients  
> anyway.
>
> Greets,
>    Helge



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/