[dev] Kronolith idea

[Duck]

On Monday 03 July 2006 18:08, Chuck Hagenbuch wrote:
> Also, like I said, we already can cache remote calendars easily, which
> is probably the biggest performance and resource saver of any of
> these. If we have to make registry calls on every calendar load,
> that's worse than generating a remote cal once and displaying it a few
> times. And if we're going to add caching for these api calls, that's
> just additional code to maintain that I don't think we should have to
> bother with.

I not familiar with kronolith cache code. I guess we will again request at 
least the calendar header to see if the calendar is not changed. This will 
still produce another complete module load?

Duck