> It adds a lot of things you'd need to be careful about (e.g. how to ensure
> the data is still in shared memory between when the signal is sent and when
> the DBus slots are finally called and processed, naming the key for the
> memory segment, etc.), but the idea is sound.
The idea is to keep
On Monday, September 03, 2012 13:31:47 Ivan Čukić wrote:
> 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 d
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 access