[Chandler-dev] Things to test when changing calendar code

[Andi Vajda]

On Mon, 5 Mar 2007, Jeffrey Harris wrote:

> - Make fewer queries to the repository of what items relate to the
> current week range.  With a big calendar, those calls are expensive, and
> we make them 4-5 times per rendering of the various calendar regions
> (mini-calendar/all-day/timed canvas).  This would probably involve
> caching the relevant items, but of course invalidating the cache then
> becomes crucial.

One concrete idea that was floated earlier this morning was that the events in 
range for the all-day and timed canvases could be cached on the UI event. As 
the UI event travels from one canvas to the next the first recipient could 
compute and cache the events in range and the second one just re-use these.
Once the UI event was processed, the events cache should be discarded.

Andi..