Re: 10.000 events in a Resource Calendar

On 2012-05-22 13:38, Aleksander Machniak wrote:
> 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.
>

Of course you're right, such, whether it be a background worker process 
through FPM or other FastCGI-like implementation, or a separate daemon 
picking up on tasks in a queue, or whatnot, would enable a client to 
simply HEAD-and-ignore.

Additionally, message bus capabilities for Cyrus IMAP Andreas Osowski 
is working on merging back into upstream master would allow many more 
components to do many more things completely autonomously, where many is 
"infinite" in that it is limited to message-bus' scalability.

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08