On Sun, Dec 23, 2012, at 08:19 PM, David Faure wrote:
> On Sunday 23 December 2012 17:54:18 Christian Mollekopf wrote:
> > Another important advantage is that we can thus now also skip large batches
> > of  new/changed items, knowing they will be picked up by the
> > initial-indexing eventually.
> 
> How so? If initial == on startup of the feeder, then it might never
> happen.
> I use "suspend to RAM" every evening, for instance, so there's no
> "startup" 
> (of the workspace, or of akonadi) for 6 months or so.
> 

Yes, that initial indexing should be re-run regularly, and running it on
startup is just a first quick implementation.

I was thinking of a combination of timer and  the idle signals, so the
task is ideally re-run if the computer is idle, or after a certain
timeout.

It still a somewhat expensive operation, so we want to avoid running it
too often.

Cheers,
Christian

> -- 
> David Faure, faure@kde.org, http://www.davidfaure.fr
> Working on KDE, in particular KDE Frameworks 5
> 
> _______________________________________________
> 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/
_______________________________________________
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/