Fwd: KActivities library optimizations
ivan.cukic at kde.org
Mon Sep 3 17:23:04 BST 2012
> 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 the basic structures - the list of activities with names,
icon names and states always in the shared memory. So, not having them only
until the client retrieves them - but persistent.
The client could access the needed info nevertheless it got the signal that it
has changed or not.
Make your code readable. Pretend the next person who looks
at your code is a psychopath and they know where you live.
-- Philip Wadler
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel