Review Request: This patch adds the Storage class for Plasma::DataEngine caching. This current implementation caches to disk. Soon, it will be akonadi.
Marco Martin
notmart at gmail.com
Tue Jul 13 22:13:01 CEST 2010
On Tuesday 13 July 2010, Aaron J. Seigo wrote:
> On July 12, 2010, Marco Martin wrote:
> > a) retrieve become asymmetric with store and retrieve everything
> > while
> >
> > store does for a single key value pair
>
> that's fine.
ok, so we'll go on that route
> > b) not using a service anymore,
> > would be directly kconfig, akonadi or whatever
>
> this would be a break with the plasma architecture. first thing that
> springs to mind is that things like remote engines will no longer restore
> from cache properly. i also don't see what using akonadi directly would
> give us, as that would end up being async as well (one only hopes,
> anyways, since it is out of process). and using kconfig directly doesn't
> sound like such a hot solution either.
and are you for using akonadi at all, sticking with kconfig?
even if i don't really know it, akonadi really feels way more heavy duty and
suitable for this.
i would like to find a way to avoid the first serialization to base 64 (and
let akonady serialize or store in the most appropriate way, that maybe will
end upo base64 as well, but done a single time)
Cheers,
Marco Martin
More information about the Plasma-devel
mailing list