Re: 10.000 events in a Resource Calendar

On 05/22/2012 02:26 PM, Jeroen van Meeuwen (Kolab Systems) wrote:

> - The client triggering Free/Busy does not simply HEAD a URL and 
> disconnects, as this would impede the slice of time any web server code 
> has available to do what it needs to do. Therefore, a client keeps open 
> the connection (and uses GET/POST) until the web server performing the 
> Free/Busy updating is done. This is considered a blocking operation for 
> clients that cannot do this in the background.

This of course don't need to be true. You can design freebusy server to
just set "need update" flag in this request, so it will be very fast.
Some background worker process could update cache when it detects change
of this flag.

-- 
Aleksander Machniak
Web Developer, Kolab Systems AG
-------------------------------------------------------
PGP:19359DC1 - http://www.kolabsys.com - http://alec.pl