[Nepomuk] Activities protocol

[Sebastian Trüg]

>> Exactly. My approach was rather similar to Ivan's I think: I have a dbus
>> service that handles all the events. Apps simply call a set of methods
> 
> I'm not very fond of having apps call dbus directly. By creating the
> KActivity* classes, we can keep the dbus interface as minimal as
> possible, while the classes could handle some logic and provide
> convenience methods. (and we don't need to keep the dbus api
> back-compatible)

The advantage of a DBus API is simple: we could make it a freedesktop
standard and share interfaces with systems like Zeitgeit.

>> maybe we could drop that for 4.6 since optional nepomuk makes everything
>> so much more complicated.
> 
> I agree. We'll just need to communicate this to KWin guys - they
> didn't really want to depend on nepomuk.
> 
> Although, (from my pov) the kded daemon could access nepomuk directly
> instead of doing it via the service... (it doesn't really matter
> whether it is a kded module or a nepomuk service...)

that is what I think, too.