Re: 10.000 events in a Resource Calendar

Christian Mollekopf <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab,gmane.comp.kde.kolab.devel
Organization Kolab Systems AG
Message-ID <2857247.b1qoCqjaYF@myhost2>
On Saturday 19 May 2012 12.10:29 Jeroen van Meeuwen wrote:
> Hi there,
> 
> I'm attempting to develop the code that is going to do resource management
> as defined in [1], as far as the server-side components are involved that
> is.
> 
> For testing purposes, I'm inserting 10.000 events into a resource calendar,
> all Kolab format version 3 of course. 10.000 is a lot to start with,
> 
> Given an iTip message (to which a resource is "invited"), I want to see if
> there's a conflict with any of the existing events in the Calendar.
> 
> To that end, I was wondering if there's a way to do this more efficiently
> than;
> 
> 1) Obtain *all* event objects,
> 2) Parsing *all* of them one by one,
> 3) Until I find a conflict or run out of events.
> 
> Any thoughts would be appreciated.
> 

The only option I see is a cache which can be queried.
If we had a sorting of the objects according to the start-date we could search 
them quicksort-style, but otherwise I don't see any other possibility.
IMO such a cache would ideally be implemented as akonadi agent, which 
basically builds an in-memory calendar based on KCalCore.

Until then, I would suggest to go the not-so-efficient way of parsing all items 
every time.

If you can tell me what exactly you need in terms of conflict detection API, I 
can implement the required functionality in libkolab.

Cheers,
Christian

> Kind regards,
> 
> Jeroen van Meeuwen
> 
> [1] http://wiki.kolab.org/Kolab_3.0_Resource_Management#Design

_______________________________________________
Kolab-devel mailing list
[email protected]
https://www.intevation.de/mailman/listinfo/kolab-devel
signature.asc (application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEABECAAYFAk+4HsIACgkQF4TVOOpldAAxoQCgp5rmOlzpMkYSOXqgnBFEK/JT
6tEAoL3FlqBzgmB+tVpn5xdj4MORnLOy
=BmTf
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.