[Kolab-devel] Analysis of large calendar performance hit

[Stephan Buys]

Hello,

It might be worthwhile looking at the IMAP SEARCH command
for retrieving calendar entries. 

In RFC 2060, in section 6.4.4 (SEARCH). the following is mentioned
as a search parameter:

HEADER <field-name> <string>
                     Messages that have a header with the specified
                     field-name (as defined in [RFC-822]) and that
                     contains the specified string in the [RFC-822]
                     field-body.

These header fields could be set when saving/updating messages
in IMAP from the Kolab client. They can then be used as search
criteria. 

A simple string encoding for the date could be used, for example:
An RFC 822 Extension field could be used as such:

X-CalStart 20030730
X-CalEnd 20030731

Search can then be done for specific days.

Just an idea :-)

Regards,
Stephan



On Monday 21 July 2003 14:36, Arend van Beelen jr. wrote:
> Hi!
>
> (this mail has been sent to kroupware at mail.kde.org as
> well)
>
> I've been looking in the KMail sources to find why it
> takes so long to load big calendar folders. If I click a
> folder about 1000 calendar entries encoded in TNEF format,
> it takes 15+ seconds to load the calendar. I found the
> performance hit occurs in a loop in
> KMGroupware::slotInitIncidences(). If I comment the for()
> loop in that function, the hit is gone (but, of course,
> the calendar entries aren't loaded either). Do you think
> it might be possible to optimize this loop some way?
> Possibly in a way that only entries for the selected
> day(s) are loaded?
>
> Greets,
>
> Arend jr.
>
> --
> Arend van Beelen jr.
> http://www.liacs.nl/~dvbeelen
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at intevation.org
> https://kroupware.org/mailman/listinfo/kolab-devel

-- 
Stephan  Buys
Code Fusion cc.
Tel: +27 11 391 1412
Mobile: +27 83 294 1876
Email: s.buys at codefusion.co.za