Fwd: KActivities library optimizations

[Ivan Čukić]

Hi,

The latest master of libkactivities caches and pre-fetches some stuff like the
currentActivity, list of activities, list of running activities, activity
names and icons, to minimise the amount of d-bus related locks*.

What do you think of the idea to go one step further, and instead of accessing
the data via d-bus, to only use d-bus for signalling the changes, but to use
QSharedMemory for actual data access (read-only from the library).
This would remove any blocking while accessing the data, unless I'm missing
some important fact about QSharedMemory which makes it undesired.
(I don't see it much in our code)

Cheerio,
Ivan

* requested by Thomas Luebking, for KWin

--
Make your code readable. Pretend the next person who looks
at your code is a psychopath and they know where you live.
  -- Philip Wadler