On 31 March 2011 22:18, George Kiagiadakis <[email protected]> wrote: > On Fri, Apr 1, 2011 at 12:07 AM, George Goldberg > <[email protected]> wrote: >> However, is the approver actually running all the time? Or is it DBus >> activated when needed? > > Currently, neither. However, it should be activated when needed. As I > think of it, whatever component sets accounts online/offline (be it > the contact list, the presence plasmoid, or whatever else) should be > responsible for activating and deactivating the approver. This can be > done by calling kded methods over dbus: > > $ qdbus org.kde.kded /kded loadModule telepathy_kde_approver > $ qdbus org.kde.kded /kded unloadModule telepathy_kde_approver
This worries me a bit. There's going to be all manner of different presence plasmoids and other apps using telepathy in future, and I don't think we can realistically expect them to take care of starting the approver. Perhaps it could be started as part of a KDE session? Or it could be a KDED module? > >> Also, in order to get these invite signals, do we need to have any >> channels open? Or can the daemon which does it just watch the Account >> Manager, and whenever there is a connected account, connect to the >> appropriate signals to be notified when someone adds us? > > I think it is sufficient to watch the account manager. Cool. That keeps things simple then. -- George _______________________________________________ KDE-Telepathy mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-telepathy
