[Telepathy] Best way to handle the client leaking connections?

[mikhail.zabaluev at nokia.com]

Hi, this is Mikhail from Nokia.

> -----Original Message-----
> From: telepathy-bounces at lists.freedesktop.org [mailto:telepathy-
> bounces at lists.freedesktop.org] On Behalf Of ext Edward Page
> Sent: Wednesday, March 10, 2010 4:24 AM
> To: Sjoerd Simons
> Cc: telepathy at lists.freedesktop.org
> Subject: Re: [Telepathy] Best way to handle the client leaking
> connections?
> 
> > This seems to be an issue in the client. Which client are you using?
> Definately
> > this shouldn't happen if mission control is used.
> 
> This was all on Maemo 5 using the built in client (RTComm/MC ?).  I
> found a related bug report for the Skype CM and posted my findings.
> I got a response from Mikhail at Nokia pointing the blame on
> connection managers.  I have not gotten any further feedback on how a
> properly functioning connection manager should respond.

To make Mission Control happy, a connection manager should not block its internal event loop which processes D-Bus method calls, at least at the time when RequestConnection is called. If the RequestConnection D-Bus call times out, Mission control will consider the connection failed, and rightly so.
So, if you have any such kind of snags in your protocol stack, you ought to work around them. Look closely at any blocking calls performed: 1) at connect time; 2) at connection shutdown so they may leave a connection object lingering. Consider using asynchronous implementation for such functionality if available, or put it to a thread.

Hope this helps,
  Mikhail