KActivities library optimizations

[Aaron J. Seigo]

On Monday, September 3, 2012 09:26:27 Ivan Čukić wrote:
> 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).

sounds a lot less maintainable and in the long run less re-usable. i also 
wonder if using shared memory wouldn't simply move, rather than remove, lock 
contention for data population, etc.

looking at the code in kactivities, the main problem seems to be that there 
are (still) sync calls in the library. that's "ok" as long as it can be 
guaranteed that the calls return quickly, which means that a) the daemon is 
either running always (never crashes) or very quick to start, b) the daemon 
can guarantee fast retrieval of the data, c) the daemon itself is never in a 
sync call for very long.

the sync calls seem to be there due to the API of libkactivities which 
attempts to provide synchronous access. perhaps it would be better to just 
drop the pretense of synchronicity in the API?

-- 
Aaron J. Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20120904/c011da2d/attachment.sig>