[Kde-pim] [kdepim-users] KDE 4.2 KPilot coming! (how to both be excited and have realistic expectations)

[Roland Baum]

possibly solving this, by "remembering" by akonadi which application requested 
one resource within the last X <time period> and just tell this 
application(s) that data has been changed ?
this could be a compromise between telling "all" applications that data has 
been changed and "tell all applications that data has been changed if you 
didn't told them within the last X <timeperiod>" ?

greetings

roland

Am Dienstag, 27. Januar 2009 13:32:42 schrieb Kevin Krammer:
> On Tuesday 27 January 2009, Marc Deop i Argemí wrote:
> > On Thursday 22 January 2009 19:03:57 Kevin Krammer wrote:
> > > The drawback is that there will be a bit of delay between Akonadi
> > > applications, such as KPilot, applying changes to data and the KDE PIM
> > > applications "seeing" it.
> >
> > Couldn't this be solved by a dbus message "telling" all the proper apps
> > that the data has been updated?
>
> The signalling is not the problem, the file change notification takes care
> of that pretty well.
>
> The problem is not writing the data for every single change, since this
> would (a) be quite inefficient when a lot of changes happen and (b)
> currently triggers a reload in the Akonadi resource itself as well,
> potentially overwriting unsaved changes.
>
> Since I wasn't able to test the latter issue sufficiently, I'd rather kept
> the writeback delay set to "1".
> A couple of seconds might already be good enough, but the setting just
> allows minutes.
>
> We could probably interpret "0" as "10 seconds", but I didn't want to do
> that so close to the release tagging.
>
> However, the situation demonstrates nicely how much everyone will benefit
> from Akonadi :)
>
> Cheers,
> Kevin


_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/