[Kolab-devel] webclient speed/scalability issues

[Zachariah Mully]

Hello all-
	I posted awhile ago about speed issues while using the webclient
calendar. Since groupware is becoming a serious albatross around my
neck, I've done some digging and found a serious scalability problem
with the Kolab drivers in Horde. 
	AFIACT, in kronolith/lib/Drivers/kolab.php, the function 'listEvents'
is called whenever calendars are viewed. The function does not use any
date bounds on the query to generate the events list, so it returns
*ALL* calendar events past and present for every calendar in the view.
Even if the view was a single day, it'll return many years worth of data
(if available), which is then simply thrown away. 
	What I'm curious about is how other clients handle this same situation,
and how calendar views are generated in a way that doesn't require each
and every message in the store to be fetched and scanned for any
calendar operation. I'm guessing that desktop clients (Kontact,Toltec,
etc) maintain a local cache on disk of the folder that they can search
through... If not, how are you scanning the xml efficiently? I would
like to implement date limits for the listEvents function, but because
the xml is the body of the message, there isn't a good way to search for
events within a date range.

Thanks,
Zack