<br><br><div class="gmail_quote">On Thu, Mar 31, 2011 at 10:23 PM, George Goldberg <span dir="ltr"><<a href="mailto:grundleborg@googlemail.com">grundleborg@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 31 March 2011 22:18, George Kiagiadakis <<a href="mailto:kiagiadakis.george@gmail.com">kiagiadakis.george@gmail.com</a>> wrote:<br>
> On Fri, Apr 1, 2011 at 12:07 AM, George Goldberg<br>
> <<a href="mailto:grundleborg@googlemail.com">grundleborg@googlemail.com</a>> wrote:<br>
>> However, is the approver actually running all the time? Or is it DBus<br>
>> activated when needed?<br>
><br>
> Currently, neither. However, it should be activated when needed. As I<br>
> think of it, whatever component sets accounts online/offline (be it<br>
> the contact list, the presence plasmoid, or whatever else) should be<br>
> responsible for activating and deactivating the approver. This can be<br>
> done by calling kded methods over dbus:<br>
><br>
> $ qdbus org.kde.kded /kded loadModule telepathy_kde_approver<br>
> $ qdbus org.kde.kded /kded unloadModule telepathy_kde_approver<br>
<br>
</div>This worries me a bit. There's going to be all manner of different<br>
presence plasmoids and other apps using telepathy in future, and I<br>
don't think we can realistically expect them to take care of starting<br>
the approver. Perhaps it could be started as part of a KDE session? Or<br>
it could be a KDED module?<br>
<div class="im"><br></div></blockquote><div>It is a KDED Module, only one started on demand rather than on startup (I believe that's a 1 line change in a .desktop file, though don't know for sure.)</div><div> </div>
<div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>Is there protection for loading twice? and can it unload itself? </div><div>If so the logic gets pretty simple. All code that turns an account online, starts the module, and that's it.</div>
<div> </div><div>I had thought it ran on startup as opposed to on demand. Are there any downsides besides the ever so slight overhead?</div></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
><br>
>> Also, in order to get these invite signals, do we need to have any<br>
>> channels open? Or can the daemon which does it just watch the Account<br>
>> Manager, and whenever there is a connected account, connect to the<br>
>> appropriate signals to be notified when someone adds us?<br>
><br>
> I think it is sufficient to watch the account manager.<br>
<br>
</div>Cool. That keeps things simple then.<br>
<br></blockquote><div>ContactManager of each account technically, but not much harder. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
--<br>
<font color="#888888">George<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
KDE-Telepathy mailing list<br>
<a href="mailto:KDE-Telepathy@kde.org">KDE-Telepathy@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-telepathy" target="_blank">https://mail.kde.org/mailman/listinfo/kde-telepathy</a><br>
</div></div></blockquote></div><br>