[CalendarServer-dev] Hoping for a sanity check: Chapter 2

Cyrus Daboo cdaboo at apple.com
Thu Oct 16 09:55:27 PDT 2008

Hi Helge,

--On October 16, 2008 9:41:13 AM +0200 Helge Heß <me at helgehess.eu> wrote:

> But more importantely, keep in mind that the primary consumers of the
> CalServer are calendaring clients. iCal, Outlook, Thunderbird etc.
> Those clients always synchronize full calendars with their local
> cache. And run queries/reports *inside* that cache. Hence the server
> is optimized to deliver the raw data quickly to the clients. Which
> then do the actual work. Well, and this works best with plain files.

Don't forget thin clients or web clients which may have little or no cache. 
I know several groups working on web-based solutions and they nearly always 
use the time-range reporting capability of CalDAV to retrieve just the 
events they need for display purposes. Our current strategy does deal with 
that reasonably efficiently in that time-range queries are handled via an 
sqlite DB for each calendar.

Cyrus Daboo

More information about the calendarserver-dev mailing list