KActivities library optimizations

[Marco Martin]

On Tuesday 04 September 2012, Ivan Čukić wrote:
> > attempts to provide synchronous access. perhaps it would be better to
> > just drop the pretense of synchronicity in the API?
> 
> I don't like the idea of having a simple requests like activity list
> or info with async api. This would be quite imitating for simple
> clients like loopless kio_activities, or file item plugin. It would be
> nicer to have something like std::async(...some method...).
> 
> For the slower methods (linked resources, and similar), I'd go for it,
> or remove it since we IIRC don't use it in any important place.

yeah, the simplest calls indeed sucks a bit being async, but migrating some 
more complex parts to a job based interface wouldn't be too bad i think

-- 
Marco Martin