[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] [RFC] Akonadi design
From:       Tobias K˙fffff6nig <tokoe82 () yahoo ! de>
Date:       2006-05-13 9:56:56
Message-ID: 20060513095656.84627.qmail () web27711 ! mail ! ukl ! yahoo ! com
[Download RAW message or body]

--- Volker Krause <volker.krause@rwth-aachen.de>
schrieb:

> Some comments/questions:
> 
> - we need to put the filter engine in there
> somewhere (given we still want to 
> do filtering in the backend), it also needs special
> handling in the 
> notification manager (ie. send notifications after
> filtering has been 
> finished).
The filters should be part of the search provider
IMHO, because a filter (virtual folder) is a static
query, or?

> - I assume search providers will build indices for
> often used fields (eg. 
> start dates for events)?
Yes, right.

> - where do cache policies fit into this design, ie.
> which part is responsible 
> to enforcing them? i guess it would probably be best
> part of the strorage
Right, caching is done by the storage, the search
providers just do filtering.

> - we need access to partial data (eg. for header
> listing of a mail folder, 
> retrieving attachments on demand, etc.), that might
> require special support 
> by the storage.
Yes, the storage provides a simple query language,
which understands the basic mime/mail structure, so
the search provider can grep just the xml-part of the
mails to do the filtering.

Ciao,
Tobias


	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]